Managing a network overlaid on another network

ABSTRACT

Briefly, methods and/or apparatuses of overlaying a secure, connected, flexible networking structure, such as on cloud infrastructure, are described.

FIELD

The present application relates to a technique to overlay a networkingstructure and, more particularly, to overlay a private network on cloudinfrastructure.

BACKGROUND

Various advancements in networking address interoperability of one ormore devices across one or more networks. Two different physicalnetworks may communicate via a network device. A network device, such asa router, may create a hardware bridge between two networks.Additionally, a remote device, such as a device on a remote network, forexample, may communicate with a local network by executing a virtualprivate network (VPN), typically by executing a software program. Inthis context (e.g., throughout this document), the term “remote” orsimilar terms refer to the device not being a part of a particularnetwork and the term “local” or similar terms refer to a collection ofdevices, for example, that are part of that network. VPN software, forexample, may create a reasonably secure channel of communication betweena remote device and local network and may route traffic to the remotedevice. This may allow the remote device to communicate with the localnetwork as if the remote device were physically part of the localnetwork, rather than remote. Unfortunately, such approaches have variousdrawbacks.

BRIEF DESCRIPTION OF THE DRAWINGS

Claimed subject matter is particularly pointed out and/or distinctlyclaimed in the concluding portion of the specification. However, both asto organization and/or method of operation, together with objects,features, and/or advantages thereof, claimed subject matter may beunderstood by reference to the following detailed description if readwith the accompanying drawings ii which:

FIG. 1 is a schematic diagram illustrating an embodiment of a secure,connected, flexible network structure;

FIG. 2 is a schematic diagram illustrating another embodiment of asecure, connected, flexible network structure;

FIG. 3 is a schematic diagram illustrating yet another embodiment of asecure, connected, flexible network structure;

FIG. 4 is a flowchart illustrating an embodiment of a method forgenerating a secure, connected, flexible network structure;

FIG. 5 is a schematic diagram illustrating a computing environment inwhich an embodiment may be implemented.

Reference is made in the following detailed description to accompanyingdrawings, which form a part hereof, wherein like numerals may designatelike parts throughout to indicate corresponding and/or analogouscomponents, for example. It will be appreciated that componentsillustrated in the figures have not necessarily been drawn to scale,such as for simplicity and/or clarity of illustration. For example,dimensions of some components may be exaggerated relative to othercomponents. Further, it is to be understood that other embodiments maybe utilized. Furthermore, structural and/or other changes may be madewithout departing from claimed subject matter.

It should also be noted that directions and/or similar references, forexample, up, down, top, bottom, and so on, may be used to facilitatediscussion of drawings and/or are not intended to restrict applicationof claimed subject matter. Therefore, the following detailed descriptionis not to be taken to limit claimed subject matter and/or equivalents.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter. Forpurposes of explanation, specific numbers, systems and/or configurationsare set forth, for example. However, it should be apparent to oneskilled in the relevant art having benefit of this disclosure thatclaimed subject matter may be practiced without specific details. Inother instances, well-known features may be omitted and/or simplified soas not to obscure claimed subject matter. While certain features havebeen illustrated and/or described herein, many modifications,substitutions, changes and/or equivalents may occur to those skilled inthe art. It is, therefore, to be understood that appended claims areintended to cover any and all modifications and/or changes as fallwithin claimed subject matter.

Reference throughout this specification to one implementation, animplementation, one embodiment, an embodiment and/or the like may meanthat a particular feature, structure, and/or characteristic described inconnection with a particular implementation and/or embodiment may beincluded in at least one implementation and/or embodiment of claimedsubject matter. Thus, appearances of such phrases, for example, invarious places throughout this specification are not necessarilyintended to refer to the same implementation or to any one particularimplementation described. Furthermore, it is to be understood thatparticular features, structures, and/or characteristics described may becombined in various ways in one or more implementations. In general, ofcourse, these and other issues may vary with context. Therefore,particular context of description and/or usage may provide helpfulguidance regarding inferences to be drawn.

Operations and/or processing, such as in association with networks, suchas communication networks, for example, may involve physicalmanipulations of physical quantities. Typically, although notnecessarily, these quantities may take the form of electrical and/ormagnetic signals capable of, for example, being stored, transferred,combined, processed, compared and/or otherwise manipulated. It hasproven convenient, at times, principally for reasons of common usage, torefer to these signals as bits, data, values, elements, symbols,characters, terms, numbers, numerals and/or the like. It should beunderstood, however, that all of these and/or similar terms are to beassociated with appropriate physical quantities and are intended tomerely be convenient labels.

Likewise, in this context, the terms “coupled”, “connected,” and/orsimilar terms may be used generically. It should be understood thatthese terms are not intended as synonyms. Rather, “connected” if usedgenerically may be used to indicate that two or more components, forexample, are in direct physical and/or electrical contact; while,“coupled” if used generically may mean that two or more components arein direct physical or electrical contact; however, “coupled” if usedgenerically may also mean that two or more components are not in directcontact, but may nonetheless co-operate or interact. The term coupledmay also be understood generically to mean indirectly connected, forexample, in an appropriate context.

The terms, “and”, “or”, “and/or” and/or similar terms, as used herein,may include a variety of meanings that also are expected to depend atleast in part upon the particular context in which such terms are used.Typically, “or” if used to associate a list, such as A, B or C, isintended to mean A, B, and C, here used in the inclusive sense, as wellas A, B or C, here used in the exclusive sense. In addition, the term“one or more” and/or similar terms may be used to describe any feature,structure, and/or characteristic in the singular and/or may be used todescribe a plurality or some other combination of features, structuresand/or characteristics. Though, it should be noted that this is merelyan illustrative example and claimed subject matter is not limited tothis example. Again, particular context of description and/or usage mayprovide helpful guidance regarding inferences to be drawn.

It should be understood that for ease of description a network device(also referred to as a networking device) may be embodied and/ordescribed in terms of a computing device. However, it should further beunderstood that this description should in no way be construed thatclaimed subject matter is limited to one embodiment, such as a computingdevice or a network device, and, instead, may be embodied as a varietyof devices or combinations thereof, including, for example, one or moreillustrative examples.

In this context, the term network device refers to any device capable ofcommunicating via and/or as part of a network. While network devices maybe capable of sending and/or receiving signals (e.g., signal packets),such as via a wired or wireless network, they may also be capable ofperforming arithmetic and/or logic operations, processing and/or storingsignals, such as in memory as physical memory states, and/or may, forexample, operate as a server in various embodiments. Network devicescapable of operating as a server, or otherwise, may include, asexamples, dedicated rack-mounted servers, desktop computers, laptopcomputers, set top boxes, tablets, netbooks, smart phones, integrateddevices combining two or more features of the foregoing devices, thelike or any combination thereof.

A network may comprise two or more network devices and/or may couplenetwork devices so that signal communications, such as in the form ofsignal packets, for example, may be exchanged, such as between a serverand a client device and/or other types of devices, including betweenwireless devices coupled via a wireless network, for example.

A network may also include now known, or to be later developedarrangements, derivatives, and/or improvements, including, for example,past, present and/or future mass storage, such as network attachedstorage (NAS), a storage area network (SAN), and/or other forms ofcomputer and/or machine readable media, for example. A network mayinclude the Internet, one or more local area networks (LANs), one ormore wide area networks (WANs), wire-line type connections, wirelesstype connections, other connections, or any combination thereof. Thus, anetwork may be worldwide in scope and/or extent. Likewise, sub-networks,such as may employ differing architectures or may be compliant and/orcompatible with differing protocols, such as communication protocols(e.g., network communication protocols), may interoperate within alarger network. In this context, the term sub-network refers to aportion or part of a network. Various types of devices, such as networkdevices and/or computing devices, may be made available so that deviceinteroperability is enabled and/or, in at least some instances, may betransparent to the devices. In this context, the term transparent refersto devices, such as network devices and/or computing devices,communicating via a network in which the devices are able to communicatevia intermediate devices, but without the communicating devicesnecessarily specifying one or more intermediate devices and/or mayinclude communicating as if intermediate devices are not necessarilyinvolved in communication transmissions. For example, a router mayprovide a link or connection between otherwise separate and/orindependent LANs. In this context, a private network refers to aparticular, limited set of network devices able to communicate withother network devices in the particular, limited set, such as via signalpacket transmissions, for example, without a need for re-routing and/orredirecting such network communications. A private network may comprisea stand-alone network; however, a private network may also comprise asubset of a larger network, such as, for example, without limitation,the Internet. Thus, for example, a private network “in the cloud” mayrefer to a private network that comprises a subset of the Internet, forexample. Although signal packet transmissions may employ intermediatedevices to exchange signal packet transmissions, those intermediatedevices may not necessarily be included in the private network by notbeing a source or destination for one or more signal packettransmissions, for example. As another example, a logical broadcastdomain, explained in more detail herein, may comprise an example of aprivate network. It is understood in this context that a private networkmay provide outgoing network communications to devices not in theprivate network, but such devices outside the private network may notdirect inbound network communications to devices included in the privatenetwork.

The Internet refers to a decentralized global network of interoperablenetworks that comply with the Internet Protocol (IP). It is noted thatthere are several versions of the Internet Protocol. Here, the termInternet Protocol or IP is intended to refer to any version, now knownor later developed. The Internet includes local area networks (LANs),wide area networks (WANs), wireless networks, and/or long haul publicnetworks that, for example, may allow signal packets to be communicatedbetween LANs. The term world wide web (WWW) and/or similar terms mayalso be used, although it refers to a sub-portion of the Internet thatcomplies with the Hypertext Transfer Protocol or HTTP. It is noted thatthere are several versions of the Hypertext Transfer Protocol. Here, theterm Hypertext Transfer Protocol or HTTP is intended to refer to anyversion, now known or later developed. It is likewise noted that invarious places in this document substitution of the term Internet withthe term world wide web may be made without a significant departure inmeaning and may, therefore, not be inappropriate in that the statementwould remain correct with such a substitution.

Signal packets, also referred to as signal packet transmissions, may becommunicated between nodes of a network, where a node may comprise oneor more network devices and/or one or more computing devices, forexample. As an illustrative example, but without limitation, a node maycomprise one or more sites employing a local network address. Likewise,a device, such as a network device and/or a computing device, may beassociated with that node. A signal packet may, for example, becommunicated via a communication channel or a communication pathcomprising the Internet, from a site via an access node coupled to theInternet. Likewise, a signal packet may be forwarded via network nodesto a target site coupled to a local network, for example. A signalpacket communicated via the Internet, for example, may be routed via apath comprising one or more gateways, servers, etc. that may, forexample, route a signal packet in accordance with a target address andavailability of a network path of network nodes to a target address.Although the Internet comprises a network of interoperable networks, notall of those interoperable networks are necessarily available oraccessible to the public.

Although physically connecting a network via a hardware bridge is done,there may be one or more drawbacks. A hardware bridge may not typicallyinclude a capability of interoperability via higher levels of a networkcommunications protocol. A network communications protocol refers to aset of signaling conventions for communications between or among devicesin a network, typically network devices; for example, devices thatsubstantially comply with the protocol or that are substantiallycompatible with the protocol. In this context, the term “between” and/orsimilar terms are understood to include “among” if appropriate for theparticular usage. Likewise, in this context, the terms “compatiblewith”, “comply with” and/or similar terms are understood to includesubstantial compliance and/or substantial compatibility.

Typically, a network communications protocol has several layers. Theselayers may be referred to here as a network communication stack. Varioustypes of network communications may occur across various layers. Forexample, as one moves higher in a network communication stack,additional operations may be available by transmitting networkcommunications that are compatible and/or compliant with a particularnetwork communications protocol at these higher layers. Therefore, forexample, a hardware bridge may be unable to forward signal packets sinceit may operate at a layer of a network communication stack that does notprovide that capability. Although higher layers of a networkcommunications protocol may, for example, affect device communicationpermissions, user communication permissions, etc., a hardware bridge,for example, may typically provide little user control, such as forhigher layer operations. Furthermore, making changes at a hardware layermay potentially affect performance of network communications, such asfor one or more layers, for example. Another drawback, as mentionedpreviously, is that it may be difficult, time consuming and/or expensiveto setup and/or modify features of a hardware bridge without specializedskills and/or experience, such as technical know-how.

A VPN, such as previously described, may enable a remote device tocommunicate via a local network, but may also have drawbacks. A routermay allow network communications in the form of network transmissions(e.g., signal packets), for example, to occur from a remote device to aVPN server on a local network. A remote device may be authenticated anda VPN server, for example, may create a special route between a localnetwork and the remote device through an intervening router. However, aroute may be generated and/or also regenerate if the remote device ispower cycled, for example. Also, a VPN typically may affect a singleremote device, which may be limiting, for example, in some situations.Similarly, here too, as mentioned previously, it may be difficult, timeconsuming and/or expensive to setup and/or modify features of a VPNwithout specialized skills and/or experience, such as technicalknow-how.

A network may be very large, such as comprising thousands of nodes,millions of nodes, billions of nodes, or more, as examples. As thenumber of network devices communicating via a network grow, signalstransmissions via a network, such as in the form of signal packets, forexample, may begin to interfere. Thus, it may be desirable to createand/or generate a logical, private network, such as via (e.g., over) theInternet, to potentially limit the number of signal transmissions atleast partially without necessarily limiting geographies, for example,by having portions of a logical, connected, secure private network ingeographies of potential interest. In addition, it may be possible topurchase available capacity, such as memory and/or processing capacityof a third party, as examples, in separate markets, such as marketswhere costs may be more appealing, providing another potential benefit,as explained in more detail later. For example, applications, such assoftware applications, may execute above or on infrastructure, such asnetworking infrastructure and/or computing infrastructure, in a mannerto provide capabilities, such as these as well as others. Thus, forexample, one or more software applications may execute on computingand/or memory resources owned by a third party to create and/or generatea logical, private network for an entity other than the third party thatowns the computing and/or memory resources, as explained in more detaillater. In this context, networking infrastructure refers to conventionalhardware and software that is deployed or deployable to providenetworking functionality and/or network services without using orincluding components substantially in accordance with claimed subject.Likewise, in this context, computing infrastructure refers toconventional hardware and software that is deployed or deployable toprovide computing functionality and/or services without using orincluding components substantially in accordance with claimed subjectmatter.

In this context, the terms cloud, cloud computing, cloud hosting and/orsimilar terms refers to is the use of network and/or computing resources(e.g., hardware), network and/or computing applications (e.g.,software), or any combinations thereof delivered as a service over anetwork (typically the Internet), meaning here, in essence, the use ofhardware and/or software owned by one or more third parties. A benefitof use of the cloud or cloud computing is that it permits someone, suchas an entity, (e.g., a network provider, for example) to offer a productand/or service without necessarily owning the hardware and/or software,or at least large portions thereof. Thus, for example, a third partyhandles obtaining power, purchasing equipment, renting space, obtainingconnectivity, etc., etc. An example, but not the only one, includesAmazon AWS, which, for example, owns and/or provides data centers withequipment, etc., it makes available to others, as described.

Although a router may link otherwise independent LANs through routing ofsignal packets, a router may also provide some limits on signal packettransmissions to a select set of devices, such as network devices and/orcomputing devices, for example. A router may limit signal packettransmissions via implicitly or explicitly producing a broadcast domain(also referred to as BD or as a broadcast domain). In this context, theterm broadcast domain refers to a set of devices, such as networkdevices and/or computing devices, including associated services and/orsupport, occupying a network address space, such as a local networkaddress space, in which any device is able to communicate with any otherdevice in the broadcast domain without rerouting a transmission, such asa signal packet, for example. Although claimed subject matter is notnecessarily limited in scope in this respect, additional exampleembodiments of a broadcast domain (along with related technology) may bediscussed in U.S. patent application Ser. No. 13/543,729, titled“COMMUNICATION BETWEEN BROADCAST DOMAINS,” filed on Jul. 6, 2012, byHankins et al., herein incorporated by reference in its entirety andassigned to the assignee of currently claimed subject matter. Forexample, a signal packet may be transmitted to other devices in abroadcast domain without being directed or redirected via a router orsimilar device, such as a device capable of affecting routing of signalpackets, for example. Using a router or a similar device able to performnetwork address translation, portions of networks may be logicallyseparate and independent such that transmissions in the form of signalpackets transmitted by a network device on a network, for example, maynot necessarily be forwarded from the BD unless a destination having aparticular destination address of a signal packet transmission existsoutside the particular broadcast domain. In this context, a devicecapable of performing network address translation is referred togenerically as a NAT device or a NAT. The foregoing effectivelyillustrates one example of logically independent and separate (e.g.,non-overlapping) divisions of a network, in which the divisions maycomprise examples of respective broadcast domains.

Examples of broadcast domains may include logical BDs, virtual BDs,physical BDs or non-virtual BDs. For example, in this context, aphysical BD refers to a traditional BD comprising a set of physicaldevices, in which a physical device is able to communicate with anotherphysical device in the broadcast domain, e.g., as previously explained,without being rerouted. For example, a signal packet may be transmittedfrom one device in the BD to another device in the BD without beingdirected or redirected via a router or similar device, such as a devicecapable of affecting routing of signal packets, for example. Incontrast, a virtual BD refers to a BD that includes at least somevirtual components within the BD, such as a virtual device, and/or to aBD in which physical devices are linked, such as via a tunnel server,for example, as explained in more detail later. If used in a networkingcontext, rather than generically, the terms linked and/or connected,such as, for example, if used to refer to devices in separate BDs, suchas network devices and/or computing devices, refers to allowing signalpackets to communicate between broadcast domains as if the broadcastdomains are not separate, but without substantially changing thebroadcast domain configuration of the separate broadcast domains. Again,although claimed subject matter is not necessarily limited in scope inthis respect, additional example embodiments (along with relatedtechnology) may be discussed in aforementioned U.S. patent applicationSer. No. 13/543,729. The terms connected, linked, logically joinedand/or similar terms may be used interchangeably in context, such as ina networking context. Likewise, in this context, a virtual broadcastdomain may refer to a broadcast domain generated and/or created bylinking two or more broadcast domains at least for a period of time. Avirtual BD operates like (e.g., similar to) a physical BD, however, avirtual device that may be part of a BD (e.g., a virtual BD), forexample, is not necessarily associated with the same particular physicaldevices at all times. For example, a virtual device in a virtual BD, maymove from one physical device to a different physical device, as asimple example, and remain in the BD where, for example, state of thedevice, although virtual, is maintained. Thus, while a virtual device inthe BD necessarily executes on a physical device, it does notnecessarily always execute on the same physical device at all times.

A broadcast domain may also be referred to as a logical broadcast domain(also referred to as LBD). A logical broadcast domain may comprise avirtual broadcast domain and/or a physical broadcast domain. A logicalbroadcast domain that includes a virtual broadcast domain, for example,may refer to a logical broadcast domain in which spatial confines, so tospeak, of at least portions of the broadcast domain may not be entirelyrelated to a particular set of physical devices. For example, somedevices in the BD may not be consistently limited or associated with anyparticular physical devices. Some devices of the broadcast domain, forexample, may be logically independent of physical devices, as alluded toabove in connection with discussion of a virtual BD.

Along similar lines, a virtual local area network (VLAN) may, forexample, comprise a logical partition or sub-partition of an otherwisephysical LAN and/or logically joined (e.g., linked) logical partitionsor logical sub-partitions of multiple physical LANs, for example.Likewise, a virtual network may comprise a similar concept in whichlogical partitions or sub-partitions of LANs, VLANs or virtual broadcastdomains, may, for example, in an embodiment, be logically joined (e.g.,linked) at least for a period of time. A non-virtual broadcast domainsimply is another way to refer to a physical BD since it refers to abroadcast domain in which the broadcast domain devices exclude anyvirtual devices. Thus, devices in a non-virtual BD may comprise physicaldevices, such as a router, a computing platform (that includes acomputing device, for example), a network device, etc. The termbroadcast domain is also used in a generic sense meaning that it is notlimited exclusively to a broadcast type of signal packet transmissionscheme and/or may include in addition to and/or in place of a broadcast,other types of signal packet transmission schemes, such as, but notlimited to, anycast, broadcast, multicast, unicast, geocast, the like,or any combinations thereof.

A network device comprises a device capable of communicating via anetwork, as mentioned. A computing device comprises a device capable ofexecuting computations. Thus, for example, network devices may comprisecomputing devices, non-computing devices, and/or other devices. Anetwork device may comprise, as non-limiting examples, a router,gateway, hub, switch, host, mobile device, server, client, NAT device,the like, or any combinations thereof. A server, which may comprise acomputing device, may also operate as network device, by serving contentover a network. For example, a server may provide now known and/or to belater developed, service arrangements, derivatives, and/or improvements,including past, present, and/or future services comprising, but notlimited to, web services, third-party services, audio services, videoservices, email services, instant messaging (IM) services, SMS services,MMS services, voice over IP (VOIP) services, calendaring services, photoservices, database services, facsimile services, file services, domainname services, game services, printing services, proxy services, datastreaming services, peer-to-peer services, other services, the like orany combinations thereof. Examples of content may include text, images,audio, video, the like, or any combinations thereof, which may beprocessed in the form of physical signals, such as electrical signals,for example, or may be stored in memory, as physical states, forexample.

As indicated above, a logical broadcast domain refers to at least alogical division of a network comprising a plurality of network devicessuch that network devices communicating via the logical division of thenetwork may communicate with other network devices communicating via thelogical division without use of a router or other network device capableof limiting network communications and/or rerouting signal packettransmissions. For example, as a non-limiting illustration, a singlelogical broadcast domain may be constructed using multiple repeaters,hubs, NAT devices, and/or switches, whereby a network devicecommunicating via one of the multiple repeaters, hubs, NAT devices orswitches may communicate with another network device communicating viaone of the repeaters, hubs, NAT devices and/or switches.

In one example illustrative embodiment, use of a discovery device and areflecting device, may allow network devices communicating via theirrespective broadcast domains, for example, to discover and requestservices available via other network devices while still communicatingvia remote broadcast domains and potentially with less complexity,traffic and/or expense than conventional routing. In one possibleillustrative embodiment, a controller may manage a plurality ofrespective discovery and reflecting devices communicating via theirrespective broadcast domains. In still another possible embodiment, acontroller may provision one or more tunnel servers, for example, tofacilitate communications between network devices communicating as partof different broadcast domains. Likewise, in still another illustrativeembodiment, a controller may comprise a master controller that may beused to manage other controllers, for example, although there may, ofcourse, be more than one or even several master controllers in aparticular embodiment. In one or more embodiment, operations may beperformed, for example, by software implemented applications that may beexecuting on or above a software stack of a device, such as a networkdevice and/or a computing device; of course, this is not necessarilyrequired, but it may be typical in some embodiments.

For example, in an embodiment, a discovery device may comprise a networkdevice capable of communicating as part of a broadcast domain todiscover features of the particular broadcast domain without humanintervention to generate a broadcast domain configuration of theparticular broadcast domain. A discovery device may engage in a varietyof activities to accomplish this including, but not limited to any ofthe following: passively monitoring signal packets, actively probingother network devices, port scanning other network devices, queryingother network devices, querying servers, such as a domain controller orother server responsible for a directory of broadcast domain features,any combinations thereof, or other approaches. In this context, asmentioned, without human intervention indicates that processes may beexecuted without human intelligence being on hand or otherwise availableto make appropriate adaptations or changes, such as, if unanticipatedevents take place, for example. One or more processes may executesatisfactorily to accomplish a particular result, for example, withoutsuch human intelligence, interaction or direction. Thus, in a sense,processes may be performed automatically, so to speak. As previouslymentioned, in one or more embodiments, operations may be performed, forexample, by software implemented applications that may be executing onor above a software stack of a device, such as a network device and/or acomputing device; of course, this is not necessarily required, but itmay be typical in some embodiments.

Industry software applications may also assist in generating a broadcastdomain configuration. For example, Nmap, a GNU software program, writtenby Gordon Lyon (also known by his pseudonym Fyodor Vaskovich) andavailable for download, for example, at the website www.nmap.org,comprises network scanner software capable of discovering hosts and/orservices on a broadcast domain. Nmap may be executed by a computing or anetwork device to send network transmissions in the form of signalpackets to hosts on a broadcast domain and may evaluate receivedresponse packets. Nmap is at least capable of discovering a hostoperating system, names and versions of available services, estimateduptime, hardware parameters and/or other network parameters. A discoverydevice, for example, may discover a broadcast domain configurationparameter using Nmap or any other software application capable ofsimilar discovery. Thus, a software implemented application to performdiscovery, for example, may execute above or on other software of asoftware stack executing on a device, such as a computing device and/ora network device, for example. As an example, a virtual device may beexecuting discovery. Likewise, as previously indicated, in anembodiment, the virtual device may be executing on a physical deviceowned by a third party, for example; although, again, not necessarily.

Thus, in an example embodiment, a broadcast domain configuration may begenerated by a discovery device monitoring discovery signal packets viaa broadcast domain. A discovery device in an embodiment, as indicated,may comprise a network device and/or a computing device executing anappropriate software application. A discovery device may also passivelymonitor signal packets that may comprise information relative to abroadcast domain configuration. A discovery device may also activelyprobe one or more devices, such as communicating as part of a broadcastdomain or addressable via a broadcast domain. For example, a discoverydevice may port scan another device communicating as part of a broadcastdomain, or use a software application capable of accomplishing such atask, for example. In this context, a domain controller refers to anetwork device that is capable of responding to security authenticationrequests on a broadcast domain. A discovery device may request broadcastdomain configuration parameters from an active directory server or othernetwork device capable of maintaining a directory of broadcast domainconfiguration parameters. For example, a domain controller may comprisean active directory server, and a discovery device may query an activedirectory server by transmitting signal packets requesting a responsecomprising discovery signal information. Again, as indicated, a softwareimplemented application, for example, may perform operations in anembodiment.

Likewise, in another embodiment, available services via a network devicemay be determined based at least in part on which ports are open on anetwork device. Port scanning a network device may determine which portsmay be open by transmitting signal packets to request a connection witha network device on a port. A network device may respond, for example,by transmitting signal packets indicating an available connection. See,for example, RFC 793—Transmission Control Protocol, available, forexample, from the Internet Engineering Task Force (IETF), atwww.ietf.org. Signal packets comprising responses may imply that a portmay be available.

Because network port numbers may consistently map to known services, anetwork device monitoring these responses may at least in part discoverwhich services may be available via other network devices. For example,an open port 20 or 21 may imply that an FTP service may be available.Additionally, SSH may be available via port 22, Telnet may be availablevia port 23, SMTP may be available via port 25, POP3 may be availablevia port 110, or HTTPS may be available via port 443, for example. As isknown in the art, associations between port numbers and services may beconsistent, or may change over time. As associations between portnumbers and services evolve, it is intended that claimed subject matterinclude discovery of available services according to evolving industrystandards. As in known in the art, port scanning may be accomplished viaTCP scanning, SYN scanning, UDP scanning, ACK scanning, Window scanning,FIN scanning, or other scanning types or methods, as may be known in theart or may later be developed.

In another illustrative embodiment, a reflecting device may comprise anetwork device capable of communicating as part a broadcast domain andcapable of emulating a generated (e.g., other) broadcast domainconfiguration without human intervention. As previously mentioned inconnection with discussion of a discovery device, in one or moreembodiments, operations of a reflecting device may be performed, forexample, by software implemented applications that may be executing onor above a software stack of a device, such as a network device and/or acomputing device; of course, this is not necessarily required, but itmay be typical in some embodiments. In this context, the term emulaterefers to software stored or capable of executing on a physical devicein which, the software, if executed by a physical device, for example,would appear to another network device as a device other than thephysical device that is executing the software. Emulation may includeoperating as a proxy, meaning to appear as another device that may existor it may include appearing as a device that does not exist anywhere.Likewise, emulation may include appearing as an enhanced or augmentedversion of another device or as a more limited version of anotherdevice. Furthermore, the term device, unless specified to be a physicaldevice may include a virtual device or an emulated device.

In an embodiment, emulation may comprise, for example, a first networkdevice simulating another network device via a broadcast domain. Anothernetwork device, in this example, may comprise a physical network device,or a virtual network device. Therefore, the emulated device may notexist as a physical piece of hardware. The emulating device may,however, make services available via a broadcast domain by transmittingsignal packets in which, for example, requests for services may beforwarded to the emulated device to perform advertised services, forexample, if the emulated device comprises a physical device. In anotherembodiment, an emulating device may offer services via a broadcastdomain without forwarding requests to another network device.Additionally, emulation, in an embodiment, may comprise imitatinganother network device. However, another network device may existvirtually, and/or may comprise a set instructions being executed viaanother network device and/or computing device. Although services mayappear to be available via a device, the device may, therefore, in anembodiment, comprise a virtual device. For example, a softwareapplication may execute instructions such as a virtual device on orabove a software stack of a physical device.

In a possible example embodiment, a reflecting device may receive signalpackets from a discovery device communicating via a remote broadcastdomain, which may comprise a broadcast domain configuration includingfeatures of a broadcast domain, such as those disclosed below, forexample. A reflecting device may forward signal packets via a localbroadcast domain in a manner so as to emulate a generated broadcastdomain configuration.

In this context, the term logical broadcast domain configuration refersto various hardware devices, firmware, and/or software applications (ifresiding in one or more locations within a LBD so as to be capable ofbeing accessed or executed electronically, such as via a computingdevice) supporting a logical broadcast domain. As used in thisspecification, a logical broadcast domain configuration, therefore, mayinclude stored signal packets relating to one or more features of alogical broadcast domain. For example, a configuration may represent,characterize and/or specify information, although in physical form, suchas signals, related to one or more features, and/or other storedinformation, again, in physical form, such as memory states, relating toone or more features of a network device communicating via the logicalbroadcast domain, such as to represent, characterize and/or specify theone or more features of the LBD. Although claimed subject matter is notnecessarily limited in scope in this respect, additional exampleembodiments of a broadcast domain configuration (along with relatedtechnology) may be discussed in aforementioned U.S. patent applicationSer. No. 13/543,729.

For example, a broadcast domain configuration may include a subset of,and/or additions to the following non-limiting illustrative examples offeatures: one or more network protocols, available addresses, usedaddresses, topologies, devices used, such as switches or hubs,historical settings, such as for security, for a network protocol, etc.,modifications of the foregoing, user accounts, including status,authentication, etc., security settings of a broadcast domain, workgroupor domain names, device names including status, available devicefeatures, etc., services available and/or used, status of the networkdevices, as well as other features.

In one example illustrative embodiment, use of a network device, forexample, may allow network devices communicating via their respectivelogical broadcast domains, for example, to discover and/or requestservices available via network devices of another logical broadcastdomain while still communicating via their respective logical broadcastdomains, potentially at least partially with less complexity, trafficand/or expense than conventional routing. In this context, the termgateway device may also be employed to refer to a network device able tolink logical broadcast domains via a tunnel server. As a matter ofconvenience, however, it is understood that any network device mayinclude such a capability, such as, for example, if loaded with softwareproviding an appropriate capability, as described in more detailthroughout this specification. Therefore, it is not intended that theterm gateway be used in this document to exclusively refer to deviceshaving such capability. Likewise, in this context, the term linkinglogical broadcast domains refers to allowing signal packets tocommunicate between logically separate broadcast domains as if thelogical broadcast domains are not separate, but without substantiallychanging the broadcast domain configuration of the separate, logicalbroadcast domains. As mentioned, the terms connected, linked, logicallyjoined and/or similar terms are used interchangeably in context, such asin a networking context (as opposed to generically). Likewise, in thiscontext, a virtual broadcast domain may be generated and/or created bylinking logical broadcast domains at least for a period of time. It isalso noted that in an embodiment or implementation, a logical broadcastdomain may comprise a single and/or remote stand-alone device.

Thus, in one embodiment, devices communicating as part of a virtualbroadcast domain, may communicate with devices operating as part of anon-virtual broadcast domain, respectively, for example. In oneillustrative embodiment, this may be accomplished via use of a tunnelserver linking several network devices, for example. A tunnel servermay, for example, execute software capable of receiving and/or sendingsignal packets from network devices in different logical broadcastdomains. Different logical broadcast domains may otherwise use separaterouters, for example. Typically, therefore, different logical broadcastdomains may occupy separate network address spaces, such as separate IPaddress spaces, as an example. Also, typically, routers may providenetwork address translation so that signal packets may be properlyrouted after leaving a particular logical broadcast domain. However, if,for example, separate routers for respective BDs include a routingtable, or similar mechanism, such that signal packets intended to reachanother logical broadcast domain are routed to a tunnel server, in thisexample embodiment, as a result, network address translation may beby-passed. Network devices in separate logical broadcast domains may,therefore, communicate with and/or via a tunnel server. A tunnel servermay forward traffic (e.g., signal packet transmissions) between gatewaydevices, for example, such as for communications between differentlogical broadcast domains. Although claimed subject matter is notnecessarily limited in scope in this respect, additional exampleembodiments of a tunnel server (along with related technology) may bediscussed in U.S. patent application Ser. No. 13/675,552, titled“LINKING LOGICAL BROADCAST DOMAINS,” filed on Nov. 13, 2012, by Hankinset al., herein incorporated by reference in its entirety and assigned tothe assignee of currently claimed subject matter.

Thus, for example, if a virtual broadcast domain provides a signalpacket A to a tunnel server, it may be encapsulated. Likewise, if anon-virtual broadcast domain provides a signal packet B to a tunnelserver it may be encapsulated. However, in this embodiment, a tunnelserver may likewise remove encapsulation (e.g., referred to astermination) to determine where to forward a signal packet andre-encapsulate it for forwarding. It is noted that the encapsulation isa term of art, but may take a variety of forms. Claimed subject matteris not intended to be limited to a particular form of encapsulation.Likewise, in an embodiment, as a few non-limiting illustrative examples,encapsulation may include encryption as well, and/or may separateencapsulation from termination. Of course, use of gateway devices,network devices and/or tunnel servers may involve much more complexnetwork transmission and/or routing arrangements as well. The previousdescription is simplified for purposes of illustration and, therefore,is not intended to be limiting.

In one possible illustrative embodiment, a controller may manage aplurality of respective gateway devices communicating via theirrespective logical broadcast domains. In still another possibleembodiment, a controller may provision one or more tunnel servers, forexample, to facilitate communications between network devicescommunicating as part of different, respective logical broadcast domains(e.g., gateways in respective LBDs may communicate via a tunnel server).Likewise, in still another illustrative embodiment, a controller maycomprise a master controller that may be used to manage othercontrollers, for example, although there may, of course, be more thanone or even several master controllers, as well as several privatenetworks, in a particular embodiment. As shall become clear later, in anembodiment, although subject matter is not limited in scope in thisrespect, use of a controller may provide a capability for centralizedmanagement of a private network, for example. In an embodiment, forexample, this may at least partially, for example, include one or moresoftware implemented applications.

The term tunnel server refers to a mechanism or technique capable ofbeing implemented in a network, such as in software, firmware, hardwareor any combination thereof (other than software per se, since softwareis executed, of course, typically on one or more computing devices),that includes a capability to link logical broadcast domains, such asvia encapsulation of signal packets, as previously described, forexample. For example, a tunnel server may comprise a softwareapplication initiated by a controller, but potentially executedelsewhere, such as on a separate server. Throughout this document theterm software application and/or software implemented application isunderstood to also encompass more than one software application and/ormore than one software implemented application. For example, in anembodiment, a tunnel server may be implemented as a virtual deviceexecuting on one or more servers owned by one or more third parties;although claimed subject matter is not limited in scope in this respect.Furthermore, in another embodiment, a tunnel server may comprise anetwork device physically, logically, virtually or non-virtuallyseparate from a controller. Likewise, a tunnel server may executeadditional services. For example, in an embodiment, a tunnel service mayalso include a capability to implement a private network policy andinspection. In this context, the term private network policy andinspection refers to a capability to implement a unified networkingpolicy, despite potentially being physically or logically separatenetworks and/or physically or logically separate sub-networks, forexample. Furthermore, implementing a private network policy andinspection includes a capability for selected networks and/orsub-networks to implement selected policies or for selected networksand/or sub-networks to implement or employ a unified policy. Selectednetworking policies or a unified networking policy may, for example,include particulars regarding implementing at least one of the followingprocesses: virus scanning, authentication, filtering (including URLfiltering, for example), deep packet inspection, encryption, a firewall,or any combinations thereof.

Likewise, in an embodiment, a gateway device may comprise a networkdevice capable of communicating as part of a broadcast domain todiscover features of another broadcast domain without humanintervention, such as, for example, to generate a broadcast domainconfiguration of another broadcast domain. Although claimed subjectmatter is not necessarily limited in scope in this respect, additionalexample embodiments of a broadcast domain configuration (along withrelated technology) may be discussed in aforementioned U.S. patentapplication Ser. No. 13/543,729. As described previously, the termgateway device is introduced as a matter of convenience; it is intendedthat within this specification any network device may include such acapability, such as via one or more software implemented applications,for example. For example, a network device may engage in a variety ofactivities to accomplish this including, but not limited, to any of thefollowing: passively monitoring signal packets, actively probing othernetwork devices, port scanning other network devices, querying othernetwork devices, querying servers, such as a domain controller and/orother server responsible for a directory of broadcast domain features,any combinations thereof, or even other approaches. Thus, although agateway device may be referred to as a matter of convenience inconnection with a broadcast domain, for example, it is to be understood,of course, that a gateway device is provided as merely one illustrationof a network device, such as a network device with capability to performoperations, as described, for example, such as, discovery, reflection,communication with a tunnel server, operating as a tunnel server,operating as a controller, etc. Likewise, a network device may beimplemented virtually (e.g., logically) or non-virtually (e.g.,physically). Furthermore, in this context, without human interventionindicates that processes may be executed without human intelligencebeing on hand or otherwise generally available to make appropriateadaptations or changes, such as, if unanticipated events take place, forexample. Throughout this specification, unless otherwise stated, it isintended that a process or processes be interpreted as being executedwithout human intervention. Thus, one or more processes may executesatisfactorily to accomplish a particular result, without humanintelligence, interaction and/or direction, for example. Thus, in asense, such processes at least may be said to be performedautomatically. Typically, although not necessarily, this may include oneor more software implemented applications.

As previously described, in an embodiment, for example, a controller mayprovide a capability of centralized management of a private network,such as a network comprising at least two logical broadcast domains, forexample. As suggested, although claimed subject matter is notnecessarily limited in this respect, in an embodiment, for example, acontroller may be implemented via a server that may be associated with anode on the Internet, for example. However, as also suggestedpreviously, management of a network, such as a private network, (whichmay, as simply an example, comprise a communications network for abusiness or an entity, for example) conventionally or typically involvessome depth of technical knowledge and/or experience, such as typicallymay reside in a company's IT department, for example. Unfortunately,however, for small businesses or the like, as non-limiting examples,such knowledge, experience and/or capability may at least in somerespects be out of reach, as a result of overhead expense, for example,that may accompany maintaining such a department.

One advantage of employing approaches consistent with embodimentspreviously discussed and/or related subject matter may be that acommunications network may be initiated, expanded, modified and/ormaintained yet still realize an associated reduced cost and/orperformance improvement in comparison with traditional, conventional orstate of the art networking approaches. Of course, medium or large sizebusiness may also benefit from such as approach. As will be discussed,additional advantages may also be present in an embodiment.

Possible benefits depending, of course, on particulars of an embodimentmay include, for example, providing essentially a “turnkey” mechanism tobring “online” a private network of potentially worldwide geographicalscope with roughly little more than an amount of technical knowledgeusually employed to operate a standardly available web browser on astandardly available computing device, for example, such as the amountof technical knowledge employed to participate in a social network, suchas Facebook or Google+, as simply illustrative examples. Thus, in anembodiment, a private network “in the cloud” may be managed via a GUIessentially as easily as it is to “friend” someone via Facebook, forexample. Furthermore, in some embodiments, for example, hardwareinstallation or even ownership may not necessarily be involved, asalluded to previously and explained in more detail later. Likewise, asalluded to, an embodiment of a private network in accordance withclaimed subject matter, for example, may be secure, seamless, scalableand provide real-time, nearly instant (e.g., on demand) service.

As alluded, embodiments, for example, may be of benefit to smallerbusinesses, entities or the like, that typically may not have sufficientresources to finance or maintain an IT department on even a modest scale(although, as indicated, larger businesses may likewise benefit).Likewise, as also alluded, embodiments may leverage, for example, commonplace technical knowledge possessed by individuals, for example, such asthose who may not be technical professionals and/or may possess apassing familiarity with computing and/or network communicationstechnology (e.g., an amount of familiarity to use conventional computingdevices, such as laptops, for example, and/or to communicate with othersvia those devices, etc.), but little more. Of course, it is alsoappreciated that these are merely illustrative examples and it is notintended that claimed subject matter be limited in scope to examplesprovided merely for illustrative purposes

To provide only a few non-limiting examples here, in an embodiment,simple, but also seamless management capabilities may include:provisioning and/or removing computing and/or memory resources,provisioning and/or removing technical services, provisioning and/orremoving software applications, adding and/or removing network users,adding and/or removing network devices, structuring groups of usersand/or devices, such as for merger and/or segregation for on-goingbusiness projects, etc. As suggested, in this context, in general,resources refer to physical resources, such as may be provided byhardware (e.g., additional memory and/or processing capability).Likewise, in general, applications refer to software-relatedapplications (e.g., at least partially implemented via software). Theterm ‘services’ refers generally to provisioning a capability for use,such as via a particular private network, which may, for example,include provisioning of resources and/or applications for use.

For example, in an embodiment, to manage a private network, such as oneincluding at least two LBDs, for example, signal packet transmissionsthrough a network may be initiated via (e.g., from) a network device.The initiating network device, nonetheless, need not be included in theprivate network. Devices included in a private network, as previouslydiscussed, refers to a particular, limited set of network devices ableto communicate with other network devices in the particular, limitedset, such as via signal packet transmissions, for example, without aneed for re-routing and/or redirecting such communications. In contrast,however, a device not included in the private network may be capable ofbeing employed in management of the private network, without necessarilybeing a device within the private network. Of course, likewise, a devicewithin the private network may also be capable of being employed tomanage the private network. Likewise, one or more third party devices,such as a virtual device executing on one or more third party servers,as an example, may be employed.

For example, in an embodiment, a network device may be associated with anode and a controller may be associated with another node. Althoughclaimed subject matter is not limited in scope in this respect, thus, inone example, the network device and the controller may respectively beassociated with separate nodes, the nodes being accessible via theInternet, as an illustration. Thus, signal packet transmissions may beinitiated from a network device to a controller, for example. In thisexample, a controller may comprise a mechanism for centralizedmanagement of a private network, such as previously described. Forexample, a controller may be implemented on a server, as one example,mentioned previously. Typically, but not necessarily, a controller mayexist virtually, and/or may comprise a set instructions being executedvia a device, such as a network device and/or computing device. Althougha controller may appear to be available, the device may, in anembodiment, comprise a virtual device. For example, a softwareapplication may execute instructions such as a virtual device on orabove a software stack of a physical device.

A network device, such as described in this example, typically mayinclude a GUI, so that rendering of the GUI may take place. Of course,any one of a host of mechanisms to accomplish this are possible. Forexample, a standard web browser may be employed to render a GUI. A GUI,for example, may be rendered on a network device and/or a computingdevice based at least in part on signal packet transmissions to thedevice that may be initiated by a controller, for example. Thus, aclient-server model in which, for example, a controller serves contentto a client may be employed to render a GUI on a network device via aconventional browser without a plug-in, for example. Alternately, aplug-in may be employed to facilitate rendering of a GUI. In stillanother possible embodiment, a device, such as a network device and/orcomputing device, may include native software to render a GUI. These, ofcourse, are merely illustrative examples and claimed subject matter isnot restricted in scope to these or any other particular approaches, nowknown or later developed, that may be employed to render a GUI on adevice having a display, such as on a network device, for example.Although in this example, the Internet was discussed, in an alternativeembodiment, of course, the network may comprise any network, such as astand-alone private network, an Intranet, a local area network, a widearea network, etc. Thus, as alluded to previously, a device, such as anetwork device and/or a computing device, to manage a private networkmay be included within the private network, but is not necessarily so.

As suggested previously, signal packet transmissions may be initiatedfrom a device, such as a network device and/or a computing device.Initiated signal packet transmissions may be of use at least in part interms of management of a private network, such as one comprising atleast two or more logical broadcast domains. Again, as one simple andnon-limiting example, initiated signal packet transmissions may resultin a controller generating a separate logical broadcast domain thatincludes several devices that are included in a particular privatenetwork and are accessible to a controller of that network, for example.Similarly, but alternately, initiated signal packet transmissions mayresult in a controller generating a separate logical broadcast domainthat includes several users for a private network, where, for example,users may be accessible via devices on the private network, the devicesbeing associated with the users.

Although the previous example referred to a single device, of course,multiple devices may respectively have GUIs with similar capabilities.Likewise, an embodiment may involve multiple private networks.Furthermore, although a network device and/or a computing device maycomprise a physical device; likewise, a device may comprise a virtualdevice in an embodiment, such as previously indicated. Along similarlines, in a generated LBD, as discussed above, one of the devicesassociated with one of the users may comprise a physical device, avirtual device or a user may, for example, have both an associatedphysical device and another associated virtual device, as an example.

In an embodiment, a device may relationally depict or display a network,such as a private network, in terms of users on the network, rather thanin terms of devices on the network. One possible advantage includes acapability to thereby manage the network in a manner more in terms ofthe particular trait being depicted. For example, a network may bemanaged or oriented with respect to users, rather than devices, whichmay, in some situations or environments, turn out to be more useful ordesirable. It is noted that the terms depict, display or similar termsmay be used interchangeably. Although claimed subject matter is notnecessarily limited in scope in this respect, additional exampleembodiments of a broadcast domain configuration (along with relatedtechnology) may be discussed in U.S. patent application Ser. No.14/763,805, titled “PEOPLE CENTRIC MANAGEMENT OF CLOUD NETWORKS VIAGUI”, filed on Jan. 22, 2013, by Cartsonsi et al., herein incorporatedby reference in its entirely and assigned to the assignee of claimedsubject matter.

In an example embodiment, a database, such as a relational database, maystore network-related associations (e.g., traits), for example.Therefore, in an illustrative, yet simplified embodiment, a device maydisplay a relational GUI. For example, a depiction of a network may berendered in terms of users, for example. However, it may be desirable tosee a display of geographies in which those users are located, forexample. In an embodiment, manipulation of a relational GUI on a devicemay result in querying a relational database. Signal packettransmissions from a controller may provide query results and arelational GUI may re-render a display of a network of users in terms ofgeography. Again, this is merely an illustrative, yet simplified,example and it is not intended that claimed subject matter be limited tosimplified, illustrative examples, of course.

An example of an embodiment of a private network, such as at least twoLBDs, is discussed below. FIG. 1 is a diagram illustrating anembodiment. For example, in an embodiment, one or more networks may beoverlaid on or above network connectivity via networking infrastructureand/or computing infrastructure in a manner so as to form a connected,secure private network, as mentioned previously. The one or moreoverlaid private networks typically are implemented via one or moresoftware implemented applications, for example.

As shall be seen, such a network may also be flexible (e.g.,reconfigurable in real-time). Of course, claimed subject matter is notlimited in scope to examples or illustrations, such as discussed below,for example. Rather, typically, examples or illustrations may besimplified for ease of understanding, for example. In this context,network connectivity refers to the presence of sufficient connectivityamong devices of a network or sub-network to support networkcommunications. In this context, networking infrastructure refers toconventional hardware and software that is deployed or deployable toprovide networking functionality and/or network services without usingor including components substantially in accordance with claimedsubject. Likewise, in this context, computing infrastructure refers toconventional hardware and software that is deployed or deployable toprovide computing functionality and/or services without using orincluding components substantially in accordance with claimed subjectmatter. Thus, overlaying one or more networks, such as a private networkon or over connectivity via infrastructure (and/or one or more networksbeing overlaid on or above) refers to creating and/or generating aprivate address space within a network. For example, in an embodimentencapsulation may be employed in a manner so that the one or moreprivate networks reside on or above another network that includesanother network address spec, for example. In an embodiment, for aninteroperable system of software applications, software implementedapplications may be employed in connection with the one or more privatenetworks, such as executing as a virtual device on a computing deviceand/or network device, although, of course, this is not required and ismerely one example.

As suggested previously, management of a network, such as a privatenetwork, (which may, as simply an example, comprise a communicationsnetwork for a business or an entity, for example) conventionally ortypically involves some depth of technical knowledge and/or experience,such as typically may reside in a company's IT department, for example.Unfortunately, however, for small businesses or the like, asnon-limiting examples, such knowledge, experience and/or capability mayat least in some respects be out of reach, as a result of overheadexpense, for example, that may accompany maintaining such a department.

One advantage of employing approaches consistent with embodimentspreviously discussed and/or related subject matter may be that acommunications network may be initiated, expanded, modified and/ormaintained yet still realize an associated reduced cost and/orperformance improvement in comparison with traditional, conventional orstate of the art networking approaches. Of course, medium or large sizebusiness may also benefit from such as approach. As will be discussed,additional advantages may also be present in an embodiment.

Possible benefits depending, of course, on particulars of an embodimentmay include, for example, providing essentially a “turnkey” mechanism tobring “online” a private network of potentially worldwide geographicalscope with roughly little more than an amount of technical knowledgeusually employed to operate a standardly available web browser on astandardly available computing device, for example, such as the amountof technical knowledge employed to participate in a social network, suchas Facebook or Google+, as simply illustrative examples. Thus, in anembodiment, a private network “in the cloud” may be managed via a GUIessentially as easily as it is to “friend” someone via Facebook, forexample. Furthermore, in some embodiments, for example, hardwareinstallation or even ownership may not necessarily be involved, asexplained in more detail. Likewise, as alluded to, an embodiment of aprivate network in accordance with claimed subject matter, for example,may be secure, seamless, scalable and provide real-time, nearly instant(e.g., on demand) service.

Likewise, in an embodiment, a private network may include one or morevirtual network portions. A virtual network portion, likewise, mayinclude one or more virtual devices. Virtual devices were discussedpreviously. For example, a virtual device in a virtual BD, may move fromone physical device to a different physical device, as a simple example,and remain in the BD where, for example, state of the device, althoughvirtual, is maintained. Thus, while a virtual device in the BDnecessarily executes on a physical device, it does not necessarilyalways execute on the same physical device at all times.

Furthermore, in an embodiment, the private network may comprise adynamic network. Thus, as alluded to, the network, or a portion thereof,such as a sub-network, may be configured or re-configured in real-time.As on example, discussed in more detail later, the private network maybe configured or reconfigured geographically for any one of a host ofpossible reasons, including to improve performance and/or reduce costs.For example, as a non-limiting illustration, a private network may bereconfigured if throughput for a route through a provisioned tunnelserver begins to drop below an acceptable level. Likewise, as discussedin an example, infra., reduced proximity between gateway devices and aprovisioned tunnel server may reduce latency, for example. Of course,these are merely a few illustrative examples. Many more are possible andclaimed subject matter is not limited in scope to illustrations.

As mentioned, a secure, connected private network may be overlaid on orover network connectivity via networking and/or computinginfrastructure. Here, as mentioned, this includes conventionalnetworking and computing hardware and software. Likewise, it may includeone or more servers owned by one or more third parties. Thus, softwareimplemented applications may include one or more virtual devices, asmentioned above, executing on one or more servers owned by one or morethird parties, for example. As alluded to previously, a virtual devicemay execute on or above a software stack, for example. In an embodiment,the one or more virtual devices may include one or more tunnel serversprovisioned, such as by a controller, for example. Likewise, the one ormore virtual devices, or other virtual devices, may include one or morecontrollers, such as a master controller. Furthermore, in an embodiment,a tunnel server and a controller may be combined as part of a virtualdevice, for example.

Likewise, a tunnel server may perform other services, as well. Forexample, in an embodiment, a tunnel service may also include acapability implement a private network policy and inspection process,which may, for example, including a unified networking policy, despitepotentially being physically or logically separate networks and/orphysically or logically separate sub-networks, for example. A privatenetwork policy and inspection process may also include for selectednetworks and/or sub-networks employing selected policies or selectednetworks and/or sub-networks employing a unified policy. Selectednetworking policies or a unified networking policy may, for example,include particulars regarding implementing at least one of the followingprocesses: virus scanning, authentication, filtering (for example, URLfiltering), deep packet inspection, encryption, a firewall, or anycombinations thereof, as examples. Likewise, in an embodiment, one ormore tunnel servers may, for example, perform network addresstranslation.

As indicated previously, a private network may comprise at least twological broadcast domains. Thus, in an embodiment, for example, one ormore overlaid networks may include a capability to perform discovery andreflection of at least one of the at least two logical broadcastdomains, of both of at least two LBDs, or of some or even of all LBDswhere there may be more than two. In an embodiment, at least two logicalbroadcast domains forming an overlaid private network may be virtuallylinked, such as previously described. For example, in an embodiment, atunnel server may be employed to link two logical broadcast domains.Thus, in an embodiment, for example, one or more overlaid privatenetworks may include a capability to bypass routers performing networkaddress translation. One potential benefit, although claimed subjectmatter is not limited in scope in this respect, may include potentiallyreduced network traffic at least in connection with network discovery,for example.

Another potential benefit, although again, claimed subject matter is notlimited in scope in this respect, may include a capability to executedeployment of network services and/or network resources, as described inmore detail, in particular on demand deployment. As suggested, in thiscontext, in general, resources refer to physical resources, such as maybe provided by hardware (e.g., additional memory and/or processingcapability). Likewise, in general, applications refer tosoftware-related applications (e.g., at least partially implemented viasoftware). The term ‘services’ refers generally to provisioning acapability for use, such as via a particular private network, which may,for example, include provisioning of resources and/or applications foruse.

In an embodiment, the capability to execute on demand deployment ofnetwork services and/or network resources may include marginal networkresource allocation. As a non-limiting illustrative example, a privatenetwork or sub-network may operate more effectively if additional memoryor computing resources are brought online relatively quickly. Likewise,the capability to execute deployment of network services and/or networkresources may include network scaling, such as up scaling ordownscaling, which may also be implemented via on demand deployment ofnetwork services and/or network resources. Again, for example, ifnetwork utilization or network packet latency increases or decreases toan extent that may result in a noticeable effect on network performance,scaling up or scaling down resources as appropriate may be handled inreal time, for example. Furthermore, in an embodiment, one or moreoverlaid private networks may include a capability to execute deploymentof network services and/or network resources without human interventionbased at least in part on a measured increase in network utilizationand/or network latency, a measured reduction in network bandwidth or anycombinations thereof. For example, without limitation as an illustrativeexample, network traffic may be monitored and/or measured.

In connection with monitoring network traffic various parameters may bemeasured. As a non-limited list of examples, average throughput in aparticular unit of time, real-time through put, average utilization in aparticular unit of time, real-time utilization, average latency in aparticular unit of time and/or real-time latency of networkcommunication packets may be monitored and/or measured. In addition,measurements may be taken over different routes, over a complete loop,over the entire private network, over sub-networks, over a logicalbroadcast domain, between any two or more nodes, etc., etc. These arejust a few examples of the almost limitless set of measurements that maybe computed for a private network. Likewise, therefore, an embodimentmay also include a capability to reconfigure the private network withouthuman intervention to improve network performance and/or to reducenetwork cost and/or a capability to reconfigure the private networkincluding reallocation of network resources and/or geographicalreconfiguration of the private network, such as substantially inaccordance with various measured network performance and/or costparameters so as to result in adjustment and/or tuning thereof.

Referring to FIG. 1, LBDs 209, 210 and 214 are illustrated, for example.A controller 206 and a tunnel server 260 are also illustrated, asdescribed in more detail below. In one embodiment, independent logicalbroadcast domains may exist before a virtual broadcast domain is to begenerated via linking LBDs, for example; although “pre-existing” BDs isnot intended to be a requirement. Gateway devices (GDs) 215, 211, and208 may be included within respective LBDs or may be generated orproduced, such as, in one example embodiment, through installation of asoftware application on a device, such as a network device, for example,or through another mechanism. GDs 215 and 211 may communicate withcontroller 206 in one embodiment. Gateway devices 211 and 215 may, forexample, transmit a broadcast domain configuration to controller 206.Likewise, controller 206 may provision tunnel server 260 and may notifygateway devices 211 and/or 215 of a network address for tunnel server260. Likewise, tunnel server 260 may link logical broadcast domains 214and 210, in an embodiment. Tunnel server 260 may in another embodimentalso link more than two independent logical broadcast domains, such asmore than two pre-existing LBDs, for example. Again pre-existing BDs arediscussed for illustration purposes, but being pre-existing is notintended as a requirement.

Gateway devices 211 and 215 may transmit signal packets comprising abroadcast domain configuration to tunnel server 260. A tunnel server mayforward signal packets, previously received, for example, that maycomprise a broadcast domain configuration, such as via forwarding fromgateway device 211 to gateway device 215, for example. A tunnel server,such as 260, may also forward signal packets, previously received, forexample, that may comprise a broadcast domain configuration, such asforwarding to gateway device 211, for example. A virtual broadcastdomain (VBD), therefore, may be generated at least for a period of timeby linking logical broadcast domain 214 and logical broadcast domain210, for example, to generate a private network.

Depending at least in part on particulars of an embodiment, gatewaydevices, such as 211 and 215, for example, may, in an embodiment,emulate a received broadcast domain configuration, as shall be explainedin more detail infra., and as may be discussed, for example, (along withrelated technology) in previously referenced U.S. patent applicationSer. No. 13/543,729, titled “COMMUNICATION BETWEEN BROADCAST DOMAINS,”filed on Jul. 6, 2012, by Hankins et al., which is assigned to theassignee of the presently claimed subject matter and is hereinincorporated by reference in its entirety; however, these examples,including examples from U.S. patent application Ser. No. 13/543,729, ofcourse, are simply provided as illustrative examples and are notintended to limit claimed subject matter in scope. Gateway devices 211and 215 may, for example, emulate a received broadcast domainconfiguration from other sources, such as, but not limited to,controllers, tunnel servers, other gateway devices, etc., for example.In a similar manner, more than two logical broadcast domains may belinked, such as previously mentioned. A gateway device may receive abroadcast domain configuration from a plurality of other gateway devicescommunicating entirely, primarily or at least partially via otherlogical broadcast domains, for example.

In one embodiment, as previously disclosed, responsive to initiatedsignal packets, a controller may initiate instructions for gatewaydevices, such as 208, 211, and 215, for example, to communicate withand/or via a tunnel server, such as 260, for example. Gateway devices208, 211, and 215 may communicate with and/or via a tunnel server, suchas 260. Gateway device 211 may generate a broadcast domain configurationcorresponding to logical broadcast domain 210, for example. Gatewaydevice 208 may generate a broadcast domain configuration correspondingto logical broadcast domain 209, for example.

Gateway devices 208 and 211 may transmit respective generated broadcastdomain configuration to controller 206. Controller 206 may forwardbroadcast domain configurations, such as received from other gatewaydevices, for example, to gateway device 215. Gateway device 215 mayemulate multiple received broadcast domain configurations as part oflogical broadcast domain 214. For example, as an illustration, networkdevice 216 may discover network device 223 communicating as part oflogical broadcast domain 209 and/or network device 212 communicating aspart of logical broadcast domain 210. As mentioned, although notnecessarily required, in an embodiment, software implementedapplications may at least partially or primarily be employed toimplement operations, such as these illustrations, for example.

Continuing with the embodiment of FIG. 1, as an illustration of onepossible scenario, network device 216 may communicate a request, such asby transmitting one or more signal packets, such as to network device223, for example. Thus, via gateway device 215, for example, one or moresignal packets comprising a request may be forwarded from network device216 to tunnel server 260. Tunnel server 260 may, as a result, forwardone or more signal packets, such as to gateway device 208, for example.Gateway device 208 may transmit signal packets via a logical broadcastdomain, here 209, for example. Since network device 223 comprises partof logical broadcast domain, it may therefore receive a request that maybe viewed as an emulation of a request from network device 216 via thenow local logical broadcast domain. Thus, network device 223 may acceptthe request and respond according to established network protocols in anembodiment, for example. In this illustrative example, a response maylikewise be forwarded back via gateway device, 208, and tunnel server260, to gateway device 215 for emulation as part of logical broadcastdomain 214. Gateway device 215 may transmit one or more signal packetsvia logical broadcast domain 214 indicating an accepted request fromnetwork device 223 to network device 216. Thus, network devices 216 and223 may communicate via a virtual broadcast domain comprising LBDs 209and 214, in this example, and by-passing NAT implemented by routers, forexample. Thus, a private network managed by controller 206 has beenillustrated by this example. In an implementation, network devices 216and 223 may or may not recognize that their transmissions are forwardedvia a tunnel server and/or to other logical broadcast domains. Asmentioned, again, in an embodiment, although not necessarily required,software implemented applications may at least partially or primarily beemployed to implement operations, such as these illustrations, forexample.

In FIG. 1, routers 202, 203, or 204, for example, may route signalpackets, such as between logical broadcast domains or to a controller,such as a master controller. Thus, a gateway device 215 may transmit agenerated broadcast domain configuration to a controller or a mastercontroller, such as 206. Controller 206 may store a generated broadcastdomain configuration received from a gateway device, such as device 215,for example, using a memory device 207. Memory device 207 may comprise alocal storage device or a non-local memory device otherwise accessibleby controller 206, for example. In an embodiment, as previouslydescribed, likewise a database associating users, devices and othernetwork-related traits may also be stored there.

In one embodiment, routers 202, 203, or 204 may employ network addresstranslation (NAT). Typically, routers that employ NAT may modify asignal packet by altering a source address of a source device that maybe part of a logical broadcast domain (likewise, a router employing NATmay also modify a destination address). Therefore, a signal packettransmission from a router employing NAT may appear as though the signalpacket originated from the router rather than having originatedelsewhere. Likewise, network devices on a logical broadcast domain mayhave an intervening router, or a similar device performing networkaddress translation, for example, between the logical broadcast domainand other networks. Therefore, other portions of a network that haveother logical broadcast domains, may not conventionally be accessible todevices operating as part of the other broadcast domains, at least notwithout some form of network address translation conventionally takingplace. Likewise, routers employing NAT also may in some situations notnecessarily allow signal packets to traverse a particular logicalbroadcast domain if the packets originate from outside the particularlogical broadcast domain (e.g., not permit signal packets to reach anetwork device that may be part of the particular LBD). However, in anembodiment, for example, such as implementing a private network, NAT maybe by-passed, such as previously described, for example. Thus, otherdevices may be accessible despite intervening routers without asignificant change in infrastructure.

While, as described NAT implemented by routers are by-passed for signalpacket transmissions within the private network, in this example;nonetheless, a NAT device may be included for connecting or linking theprivate network to the Internet, as previously suggested. Althoughclaimed subject matter is not limited in scope in this respect, asmentioned, a feature of such an embodiment, for example, may include aunified networking policy being implemented across a private network aswell as selected networking policies implemented for selected portions(e.g., selected sub-networks), as previously described. Thus, forexample, referring to FIG. 1, a NAT device 265 coupled to tunnel server260 may be able to connect a private network to the Internet byimplementing network address translation for signal packets outboundfrom TS 260 to the Internet. As shown in FIG. 1, NAT device 265 may bein communication with controller 206. Thus, controller 206, in thisexample, may exercise oversight of inbound and outbound communicationsbetween the private network and the Internet. Likewise, as previouslydescribed, a unified networking policy or selected networking policiesmay be implemented in this manner for a network or selectedsub-networks.

As discussed previously, in an embodiment, a virtual broadcast domainmay comprise logical broadcast domain 214, and logical broadcast domain210. Therefore, network device 216, communicating as part of logicalbroadcast domain 214, may discover and/or request services from amessaging server 224, communicating as part of logical broadcast domain210. Also, network device 212, communicating as part of logicalbroadcast domain 210, may discover and/or request services from a fileserver 220, communicating as part of logical broadcast domain 214. Ofcourse, claimed subject matter is not limited in scope to exampleembodiments, such as the foregoing provided for illustrative purposes,for example.

Although claimed subject matter is not limited in scope in this respect,in an embodiment, as was mentioned, a potential feature may includecentralized management, such as, for example, of a broadcast domain,and/or multiple broadcast domains, despite, for example, the distributednature of devices in the respective BDs, such as with interveningindependently managed network devices, as occurs in connection with theInternet, as one example. Additionally, in an embodiment, a secure,scalable, real-time, turnkey, web-related private network that isrelatively simple and/or easy to maintain, modify and/or manage may beset up. As mentioned, again, in an embodiment, although not necessarilyrequired, software implemented applications on or above infrastructure,such as computing and/or networking infrastructure, as well as networkconnectivity, may at least partially or primarily be employed toimplement operations, such as these illustrations, for example.

As was discussed, in an embodiment, controller 206 may be accessed via adevice, such as a network device. A controller, such as controller 206,may receive broadcast domain configurations from other gateway devicescommunicating via other logical broadcast domains, whereby more than twological broadcast domains may be similarly linked such that devicescommunicating via one of a plurality of logical broadcast domains, maydiscover and/or request services available via devices communicating viaanother of the plurality of logical broadcast domains. For example,controller 206 may also receive a broadcast domain configuration fromgateway device 208, communicating via logical broadcast domain 209.Controller 206, may also forward other received broadcast domainconfigurations from logical broadcast domains 214, or 210, for example,to logical broadcast domain 209, for example, to be emulated via gatewaydevice 208 or otherwise emulated.

Referring to FIG. 1, as previously discussed, a broadcast domainconfiguration may include devices communicating via a virtual privatenetwork (VPN), for example. In this context, a VPN refers to a mechanismin which a remote host, such as a network device, communicates with aVPN server to encrypt a communication stream in a manner so that theremote host is able to reasonably securely communicate with otherdevices of the broadcast domain and in which an intervening router has aconfiguration that allows the remote host to initiate the VPN even withnetwork address translation being implemented. A device communicatingvia a VPN, such as virtual device 222, may connect to logical broadcastdomain 214, or disconnect from logical broadcast domain 214. Likewise,as discussed with other examples, here, an example embodiment, such asthis one, may be manageable from a device, such as a network deviceand/or a computing device.

Likewise, a tunnel server may be accessed and/or managed from a device,such as a network device and/or a computing device. In one embodiment, atunnel server, such as tunnel server 260, shown in FIG. 1, for example,may be employed to also perform functions of a controller. For example,one or more software implemented applications may implement desiredoperations. Tunnel server 260 may, for example, receive a broadcastdomain configuration. Tunnel server 260 may forward one or morebroadcast domain configurations to one or more gateway devices. Tunnelserver 260 may forward one or more broadcast domain configurations basedat least in part on currently communicating devices, such as a networkdevice, or otherwise, for example, such as stored BD configurations, asanother example. Additionally, a linking table or other mechanism, forexample, may specify forwarding rules or the like, to, for example,specify linking or additional functionality, such as between logicalbroadcast domains, for example, to form a virtual broadcast domain. Inanother embodiment, tunnel server 206 may transmit a portion (e.g.,digest or subset) of a generated broadcast domain configuration. Forexample, in an embodiment, a generated broadcast domain configurationmay comprise a selection of a set or subset of features of a logicalbroadcast domain 210 to be forwarded, such as to one or more gatewaydevices, for example, by tunnel server 260, operating as a controller,in this illustrative example.

Similarly, virtual devices for a private network may also be managedfrom a network device, even a virtual network device or other virtualdevice. In an embodiment, emulation may comprise, for example, a firstdevice simulating another device via a broadcast domain. Another device,in this example, may comprise a physical network device, or a virtualnetwork device. Therefore, the emulated device may not exist as aphysical piece of hardware, although may be executed or stored on aphysical device, of course. An emulating device may, however, makeservices available via a broadcast domain by transmitting signal packetsin which, for example, requests for services may be forwarded to theemulated device to perform advertised services, for example, if theemulated device comprises a physical device. In another embodiment, anemulating device may offer services via a logical broadcast domainwithout forwarding requests to another network device. Additionally,emulation, in an embodiment, may comprise imitating another device, suchas a network device and/or a computing device. However, another devicemay exist virtually, and/or may comprise a set instructions beingexecuted via another device. Although services may appear to beavailable via a device (e.g., physical device), the device may,therefore, in an embodiment, comprise a virtual device. Likewise, assuggested previously, the virtual device may be executing on a physicaldevice owned by a third party making processing and/or memory capacityavailable for purchase, for example. Likewise, as indicated previously,for these various aspects, NAT 265 is able to provide a capability toconnect a private network to the Internet, such as under direction oroversight of controller 206, for example.

It is likewise noted that in an alternate embodiment, a NAT device maybe incorporate into a tunnel server, such as 260, for example. Likewise,as was described, a tunnel server may execute additional services.Again, although not necessarily, typically services may be implementedusing one or more software applications, as was mentioned. For example,in an embodiment, a tunnel service may also include a capabilityimplement a private network policy and inspection process, which may,for example, including a unified networking policy, despite potentiallybeing physically or logically separate networks and/or physically orlogically separate sub-networks, for example. A private network policyand inspection process may also include for selected networks and/orsub-networks employing selected policies or selected networks and/orsub-networks employing a unified policy. Selected networking policies ora unified networking policy may, for example, include particularsregarding implementing at least one of the following processes: virusscanning, authentication, filtering (for example, URL filtering), deeppacket inspection, encryption, a firewall, or any combinations thereof,as an example. A NAT device, such as 260, may be employed to maintainstate of interactions between devices in the private network and devicesoutside the private network, such as Internet host devices, for example.As a result, some trade-offs may exist regarding whether to incorporatethe NAT within the tunnel server in an embodiment. Since, if the NATfails, state may be lost between the private network and the Internet,and a disruption of service may occur until connections may bere-established.

In one possible approach, NAT functionality may be included with atunnel server, such as one tunnel server per NAT. If a server fails onwhich a TS is executed, the users on the private network are impacted,but not necessarily others. In another approach, the NAT may comprise aseparate component, such as 265, illustrated in FIG. 1, and multipletunnel servers may potentially connect to the Internet via 265, forexample. Thus, if a TS fails, but not the NAT, state is generallymaintained with the Internet; however, if the NAT fails, more users maybe impacted. In still another approach, a TS and a NAT may compriseseparate components (such as software applications executing on separatephysical devices, for example), but may still do so in one-to-onerelationship. This approach has some partial fault tolerance benefits,but may increase cost and/or complexity. Likewise, an approach otherthan one-to-one, such as two-to-one, etc., may be employed in anembodiment. Although claimed subject matter is not necessarily limitedin scope in this respect, additional example embodiments of connectingto the Internet via a NAT (along with related technology) may bediscussed in U.S. patent application Ser. No. 13/802,529, titled“CONNECTING A CLOUD NETWORK TO THE INTERNET,” filed on Mar. 13, 2012, byHankins et al., herein incorporated by reference in its entirety andassigned to the assignee of currently claimed subject matter.

In an embodiment, more than one tunnel server may be employed to link aplurality of logical broadcast domains to form a virtual broadcastdomain, although, of course, claimed subject matter is not limited inscope in this respect. FIG. 2 is a schematic diagram showing anembodiment with more than one tunnel server in one illustrativenon-limiting example. In one embodiment, for example, four logicalbroadcast domains may be in communication via more than one tunnelserver. Gateway devices 311, 321, 331, and 341 may generate a broadcastdomain configuration for their respective logical broadcast domains, forexample. Gateway devices 311, 321, 331, and 341 may forward respectivebroadcast domain configurations to controller 350. Controller 350 mayprovision tunnel server one, shown as 360. Controller 350 may initiateinstructions to gateway devices 311, 321, 331, and 341 to communicatewith tunnel server one 360. Gateway devices 311, 321, 331, and 341 maytherefore initiate communications, such as via signal packettransmissions, for example.

In one embodiment, logical broadcast domain A 310, and logical broadcastdomain B 320 may be located within a similar geographic boundary, suchas, the same building, the same city, the same state, the same country,the same continent, the same planet, or other, for example. In anembodiment, logical broadcast domain C 330, and logical broadcast domainD 340, may reside in another geographic region different from thegeographic region where logical broadcast domain A 310 or logicalbroadcast domain B may reside. In one embodiment, for example, logicalbroadcast domain A 310 and logical broadcast domain B 320 may bephysically located in Los Angeles, Calif., U.S.A, while logicalbroadcast domain C 330 and logical broadcast domain D 340 may bephysically located in New York City, N.Y., U.S.A. Of course, these aresimply examples for illustration and are not meant to be limiting in anyway.

In this embodiment, tunnel server one 360, may also be physicallylocated in Los Angeles, Calif., U.S.A. so that transmissions (e.g.,signal packets) between logical broadcast domain C 330 and logicalbroadcast domain D 340 (e.g., communicating via tunnel server one 360,located in Los Angeles), may be transmitted to Los Angeles, and back toNew York.

A path or channel for communications may potentially be enhanced bycontroller 350 provisioning an additional tunnel server located morephysically proximate to logical broadcast domain C 330 and logicalbroadcast domain D 340, for example. Controller 350 may provision tunnelserver two 370. For example, in an embodiment, provisioning a tunnelserver may be accomplished via execution of one or more softwareapplications. Controller 350 may therefore initiate instructions togateway devices 311, 321, 331, and 341 to additionally initiatecommunications with tunnel server two 370, while also continuing to bein communication with tunnel server one 360, for example. Gatewaydevices 311, 321, 331, and 341 may thus initiate communications totunnel server two 370 after being deployed. Furthermore, in anembodiment, although claimed subject matter is not limited in scope inthis respect, transmissions, such as signal packet transmissions maytake place between tunnel servers, such as 360 and 370, in this example.

Provisioning an additional tunnel server may be based at least in parton a variety of factors or considerations. For example, signal packetscommunicated via tunnel server one 360 may be a factor or aconsideration. Provisioning an additional tunnel server may likewise bebased at least in part on signals from a controller, other thancontroller 350, for example. Likewise, gateway devices may optionallycommunicate with other gateway devices, such as via tunnel server one ortunnel server two, for example, depending at least in part on a host ofpossible factors, such as, geography, latency, utilization, bandwidth(e.g., throughput), availability, efficiency, cost, etc. Furthermore,via a controller, such as 350, a private network may be reconfiguredwithout human intervention, for example, to improve performance and/orreduce cost. For example, if available bandwidth decreases, if latencyincreases, and/or if network utilization increases, controller 350 mayprovision additional tunnel servers or may provision tunnel servers in amanner to improve performance and/or reduce cost without humanintervention. Examples of possible monitoring and/or measurement ofnetwork performance and/or cost-related parameter were previouslydiscussed.

As an example, gateway device 311 may transmit signal packets to gatewaydevice 321. Gateway device 311 may transmit signal packets via tunnelserver one 360 since tunnel server one 360 is more proximate to bothgateway device 311 and gateway device 321 in this example. In anotherembodiment, gateway device 311 may transmit signal packets via tunnelserver two 370, such as if tunnel server one may be unavailable, for avariety of reasons, such as, but not limited to one or more of thefollowing situations: a software issue, a configuration issue, a powerissue, scheduled maintenance, insufficient permissions, a securityissue, other issues, or combinations thereof.

Likewise, a variety of factors or considerations may likewise affectsignal packet transmissions between already provisioned tunnel servers,such as 360 and 370, for example, in an embodiment. As a simpleillustrative example, not meant to limit claimed subject matter, atunnel server in Europe may communicate with a tunnel server in theUnited States to pass signal packet transmissions, such as from abroadcast domain in Europe to a broadcast domain in the United States;however, respective broadcast domains in Europe may communicate via thetunnel server in Europe while respective broadcast domains in the UnitedStates may communicate via the tunnel server in the United States. Forexample, again, without intending to limit claimed subject matter, itmay be that latency is potentially reduced in comparison with using onlyeither the tunnel server in Europe or only the tunnel server in theUnited States to pass signal packet transmissions from a broadcastdomain in Europe to a broadcast domain in the United States. Of course,communications may also take place between more than two tunnel serversin an embodiment.

In still another example implementation involving more than two tunnelservers, for a stream of successive signal packets to be communicatedbetween two broadcast domains, the signal packets may be communicatedusing more than one tunnel server in a manner so that immediatelysuccessive signal packets have a signal communication path that includesdifferent tunnel servers. As one non-limiting example, a first broadcastdomain may communicate signal packet transmissions to a second broadcastdomain using a plurality of tunnel servers in a manner so that, forexample, for N tunnel servers, where N is an integer greater than one,every Nth signal packet from the first broadcast domain may betransmitted to the second broadcast domain via the Nth tunnel server.Likewise, of course, every Nth signal packet from the second broadcastdomain may be transmitted to the first broadcast domain via the Nthtunnel server; however, the Nth tunnel server from the first BD to thesecond BD may not necessarily correspond to the Nth tunnel server fromsecond BD to the first BD. Of course, other approaches of distributingsignal packet transmissions across multiple tunnel servers are alsointended to be included. Implementations in which multiple tunnelservers are employed may offer a variety of potential benefits, althoughclaimed subject matter is not necessarily limited in scope toimplementations having these benefits. For example, security may beenhanced. Likewise, improved fault tolerance, redundancy and/or loadbalancing of tunnel servers may also be accomplished.

In one embodiment, tunnel server one 360, may specialize in fileserving, and tunnel server two 370 may specialize in message serving. Inan embodiment, gateway device 331, transmitting signal packetscomprising file serving, may do so via tunnel server 360 or tunnelserver 370. In general, a plurality of gateway devices may communicatewith a plurality of tunnel servers. For example, provisioning additionaltunnel servers may as one possible consideration, potentially enhancecommunications by providing alternate paths between gateway devicescommunicating as part of other logical broadcast domains that may belinked via tunnel servers. Nonetheless, one or more networks of logicalbroadcast domains and tunnel servers may be generated based at least inpart on a host of considerations, such as, for example, cost,capability, efficiency, compatibility, resources, proximity, latency,bandwidth (e.g., throughput), utilization, others or combinationsthereof. In one embodiment, network device 312 may communicate with oraccess network device 322, such as using gateway devices 311 and 321communicating via tunnel server one 360, for example. Again, typically,but not necessarily, one or more software implemented applications maybe utilized. Network device 322 may communicate with or access networkdevice 342, such as using gateway devices 311 and 341 communicating viatunnel server two 370, for example. Gateway device 311 may alsocommunicate via tunnel server one 360 and via tunnel server two 370,concurrently.

In an embodiment, a tunnel server may, for example, store one or moreservice requests, such as in local memory. In an embodiment, if multipledevices, such as a network device, request similar services, a tunnelserver may provide service, or a response to a service request to arequesting device perhaps without forwarding the service request to adevice able to initiate service, for example; however, this may vary atleast in part on particulars of a situation and/or an embodiment, forexample.

Additionally, in an embodiment, a tunnel server may acknowledge receiptof one or more signal packets before arrival at a destination device,such as a network device. For example, in one embodiment, network device332 may transmit a file, or other large amount of stored informationstates (e.g., stored as physical states in memory), for example, tonetwork device 322, such as via tunnel server one 360. In an embodiment,tunnel server one may acknowledge receipt of one or more signal packetsbefore network device 322 acknowledges receipt of the one or more signalpackets, for example. This may accelerate transmissions. For example,network device 322 may receive acknowledgement of one or more signalpackets, and transmit subsequent signal packets with less delay as aresult, for example, potentially improving wide area networkcommunications, for example

A tunnel server may also replicate services available via other networkdevices. In this context, replication comprises reading and writingstored information states (e.g., stored as physical states in memory).Replication may be desirable for a variety of reasons, including,improved consistency between two or more redundant resources, such assoftware or hardware components, improved reliability, improvedaccessibility, improved fault tolerance, or combinations thereof.Replication may comprise storage replication, and/or replication ofcomputational tasks, or may comprise active or passive replication as isknown in the art. Again, an implementation may be in accordance withexecution of one or more software applications.

In one embodiment, tunnel server two 370, may store networkcommunications. Network device 322 may comprise a file server, forexample. A device, such as network device 312, may request file servicesfrom file server 322 via tunnel server two 370. Network device 312 mayreceive requested services. Subsequently, network device 332 may requestsimilar file services from file server 322 via tunnel server two 370.Tunnel server two 370, having stored previous requests for file service,for example, may respond by providing a requested file service, withoutnecessarily communicating a request to file server 322. A tunnel servermay, for example, in an embodiment, potentially provide a fasterresponse by storing previous service requests, referred to here ascaching the previous service requests. In another example embodiment, adevice such as network device 342 may comprise a database server. Tunnelserver 370 may replicate the database (or a portion thereof) of databaseserver 342. In an embodiment, if a device, for example, were to requestdatabase services from database server 342, via tunnel server two 370,tunnel server two 370 may respond, for example, without necessarilycommunicating with database server 342.

FIG. 2 also illustrates an embodiment in which, as previously described,separate NAT devices may be employed in a one-to-one relationship withtunnel servers; although, claimed subject matter is not limited to aone-to-one relationship, as previously explained. Thus, as illustrated,NAT 365 corresponds with TS 360 and NAT 375 corresponds with TS 370.Likewise, NATs 365 and 375 also may communicate with controller 350 inthe embodiment illustrated. Therefore, benefits, such as previouslydescribed, may be available, although claimed subject matter is notlimited in this respect. As one example, a unified networking policy orselected networking policies may be implemented, such as previouslydescribed. Again, software may execute or be executable on or aboveinfrastructure to implement such policies, for example. Although claimedsubject matter is not necessarily limited in scope in this respect,additional example embodiments of connecting to the Internet via a NAT(along with related technology) may be discussed in U.S. patentapplication Ser. No. 13/802,529, titled “CONNECTING A CLOUD NETWORK TOTHE INTERNET,” filed on Mar. 13, 2012, by Hankins et al., hereinincorporated by reference in its entirety and assigned to the assigneeof currently claimed subject matter.

FIG. 4 is a flowchart illustrating an embodiment of a method ofcommunication between broadcast domains. Of course, claimed subjectmatter is not limited in scope to the particular order or arrangement ofblocks shown. Likewise, additional or replacement blocks may be includedin an embodiment, such as blocks depicting one or more operations inplace of those shown may be used in an embodiment, for example.

Referring to FIG. 4, gateway devices A and B may be included as part ofseparate logical broadcast domains in an example embodiment. As shown byblock 401, gateway device A may discover and generate a broadcast domainconfiguration without human intervention, as part of a logical broadcastdomain, for example. As shown by block 410, gateway device B maylikewise discover and generate a broadcast domain configuration as partof a logical broadcast domain, for example. At block 402, gateway deviceA may initiate transmission of a generated broadcast domainconfiguration, such as in the form of signal packets, for example, to acontroller or a master controller. At block 411, gateway device B mayinitiate transmission of a generated broadcast domain configuration,such as in the form of signal packets, for example, to a controller or amaster controller. At block 420, a controller may receive one or moregenerated broadcast domain configurations from one or more gatewaydevices, such as A and/or B, for example.

FIG. 4 shows an embodiment including the blocks described above as wellas the blocks described immediate below, starting with block 421.However, likewise, in an embodiment, a flowchart of provisioning atunnel server may begin with block 421. Of course, as indicated above,claimed subject matter is not limited in scope to the particular orderor arrangement of blocks shown. Likewise, additional or replacementblocks may be included in an embodiment, such as blocks depicting one ormore operations in place of those shown may be used in an embodiment.

Referring to block 421, for example, a controller may initiateprovisioning of one or more tunnel servers, such as for device A and/ordevice B, for example. At block 422, a controller may initiatetransmission of one or more network addresses for one or more tunnelservers to gateway device A and/or gateway device B, for example. Atblock 423, gateway devices A and/or B may initiate communication withone or more tunnel servers, for example, via one or more networkaddresses for the respective one or more tunnel servers, for example.Likewise, the gateway devices may therefore forward broadcast domainand/or Internet signal packet transmissions to the one or more tunnelservers. At block 424, one or more tunnel servers may receive signalpackets and may initiate services. Services may include, for example, aprivate network policy and inspection process, which may include, asexamples, virus scanning, filtering (for example, URL filtering), deeppacket inspection, a firewall, and others, in connection with processingof the received signal packets. Likewise, as shown at block 425, the oneor more tunnel servers may initiate forwarding of signal packets, suchas between gateway devices, such as A and/or B, for example. At block426, one or more tunnel servers may determine if any of the receivedsignal packet transmissions are between a gateway device and theInternet (e.g., one or more devices accessible via the Internet) and, ifso, may initiate forwarding of signal packets to one or more NATdevices, for example. At block 427, the one or more NAT devices mayinitiate transmission of signal packets to the Internet (e.g., to one ormore devices accessible via the Internet to which the signal packets aredirected). It is noted, that in an embodiment in which a NAT device isincorporated into a tunnel server, although this operation may occur, itmay take place as part of tunnel server operation. Therefore, again,benefits, such as previously described, may be available, althoughclaimed subject matter is not limited in this respect. For example, aunified networking policy or selected networking policies may beimplemented.

FIG. 3 is a schematic diagram illustrating still another embodiment 590of a virtual broadcast domain comprising a plurality of logicalbroadcast domains. In one embodiment, respective gateway devices (e.g.,511, 515) may generate respective broadcast domain configurations andmay, for example, initiate transmission to a controller, such as 506,for example, via a router. That is, it is not necessarily required thata tunnel server always be employed, such as, for example, if networkdevices are network addressable, such as via an IP address, for example.

Respective gateway devices (e.g., 511, 515) may request from acontroller, such as 506, broadcast domain configurations of otherlogical broadcast domains and may emulate the generated broadcast domainconfigurations via the respective logical broadcast domains of which therespective gateway devices may be a part. Likewise, a gateway devicemay, instead, request that a controller, for example, instruct a gatewaydevice to initiate transmission of a generated broadcast domainconfiguration to a requesting gateway device. In one embodiment, gatewaydevice 515 may, for example, request a generated broadcast domainconfiguration from controller 506 corresponding to non-virtual broadcastdomain 510, for example. Likewise, gateway device 511 may request agenerated broadcast domain configuration from controller 506corresponding to virtual broadcast domain 580.

In one embodiment, devices communicating as part of virtual broadcastdomain 514 may communicate with devices operating as part of non-virtualbroadcast domain 510. In one illustrative embodiment, this may beaccomplished via a tunnel server, such as 560. Tunnel server 560 may,for example, execute software capable of receiving and sending signalpackets from network devices in different logical broadcast domains thatmay otherwise use separate routers, for example. If, for example, theseparate routers include a routing table or similar mechanism such thatsignal packets intended to reach another logical broadcast domain arerouted to a tunnel server, such as 560, then, in this exampleembodiment, as a result, network address translation may be by-passed.Thus, devices, such as network devices, may communicate with tunnelserver 560 and tunnel server 560 may forward traffic between devices,such as on different logical broadcast domains.

Thus, for example, if virtual broadcast domain 514 provides a signalpacket A to tunnel server 560, it may be encapsulated. Likewise, ifnon-virtual broadcast domain 510 provides a signal packet B to tunnelserver 560, it may be encapsulated. However, in an embodiment, a tunnelserver may remove encapsulation (e.g., referred to as termination) todetermine where to forward a signal packet and re-encapsulate it forforwarding so that it may be routed via intermediate network devices.Likewise, in an embodiment, as a few non-limiting illustrative examples,encapsulation may include encryption as well, or may separateencapsulation from termination.

In an embodiment, tunnel server 560 may be controlled at least in partby a controller 506. For example, tunnel server 560 may be instructed toforward network transmission signal packets from gateway device 515 togateway device 511, and forward network transmission signal packets fromgateway device 511 to gateway device 515, for an embodiment, forexample. For an embodiment, gateway device 515 in virtual broadcastdomain 514 and gateway device 511 in non-virtual broadcast domain 510may be linked for at least a period of time, in this example, by tunnelserver 560, resulting in a path for signal packet network communicationsbetween gateway device 515 and gateway device 511 and thereby forming avirtual BD, at least for a period of time, so as to forming a secure,private network, for example.

Signal packets from gateway device 515 may comprise networkcommunication signal packets transmitted via virtual broadcast domain514 from network device 516, and signal packets from gateway device 511may comprise network communication signal packets transmitted vianon-virtual broadcast domain 510 from network device 512. Gatewaydevices forwarding signal packets, or variations thereof, as part ofrespective logical broadcast domains, for example, may allow otherdevices, such as network devices, communicating as part of therespective logical broadcast domain to communicate with network devicesin different, other logical broadcast domains as if part of a singlelogical broadcast domain but without a significant change inconfiguration etc. for the participating logical broadcast domains,referred to here as forming a virtual broadcast domain.

In an embodiment, network device 516 may access and/or communicate withmessaging server 524, and network device 512 may access and/orcommunicate with file server 520. Additionally, a virtual device 522,via a traditional VPN in this example in communication with virtualbroadcast domain 514, may access and/or communicate with network devicescommunicating as part of non-virtual broadcast domain 510, such asnetwork device 512, or messaging server 524, for example. No additionalsubstantial configuration changes or modifications are necessarilyinvolved to accomplish such as result beyond those to communicate withvirtual broadcast domain 514. In an embodiment, such as this example, avirtual broadcast domain 580, may be generated at least for a period oftime by linking virtual broadcast domain (e.g., a logical broadcastdomain) 514 with non-virtual broadcast domain (e.g., a logical broadcastdomain) 510.

Tunnel server 560 may likewise receive signal packets from devicescommunicating as part of other logical broadcast domains. For example,tunnel server 560 may receive network communication signal packets fromgateway device 515 communicating as part of virtual broadcast domain514, and also from gateway device 511 communicating as part ofnon-virtual broadcast domain 510. Tunnel server 560 may receive networkcommunication signal packets from gateway device 515 and forward networkcommunication signal packets to gateway device 511, for example. Tunnelserver 560 may also receive signal packets from gateway device 511 andforward signal packets to gateway device 515, for example. In anembodiment, this may allow gateway device 515 and gateway device 511 tocommunicate, in this example, bypassing for the respective broadcastdomains execution or implementation of NAT by routers, or another orsimilar address modification technique, for example.

In another embodiment, virtual broadcast domain 514 may employ adifferent network protocol than non-virtual broadcast domain 510, suchas a different network discovery protocol, for example. In oneembodiment, a controller, such as controller 506, may translate agenerated broadcast domain configuration, such as by modifying networktransmission signal packets comprising the generated broadcast domainconfiguration for virtual broadcast domain 514 so as to be substantiallycompatible with or substantially complaint with non-virtual broadcastdomain 510, such as, for example, its particular network discoveryprotocol. In another embodiment, a controller may initiate a gatewaydevice to modify a generated broadcast domain configuration, such as forvirtual broadcast domain 514, for example, so as to be substantiallycompatible with or substantially compliant with non-virtual broadcastdomain 510, such as, for example, its particular network discoveryprotocol. Likewise, rather than being initiated, such as by acontroller, perhaps a difference in protocol, such as a networkdiscovery protocol, may be detected, such as by a gateway device and,with or without being initiated, a gateway device may translatefeatures, such as discovery related features, of the generated broadcastdomain configuration in an embodiment. For example, in one illustrativeembodiment, devices communicating as part of virtual broadcast domain514 may perform discovery via WS-Discovery, previously referenced, anddevices communicating as part of non-virtual broadcast domain 510 may doso via Bonjour, available from Apple Inc., Cupertino, Calif., see, forexample, https://developer.apple.com/bonjour/. Thus, a gateway devicemay, for example, convert a generated broadcast domain configurationfrom WS-Discovery to Bonjour for substantial compliance or substantialcompatibility within logical broadcast domain including gateway device.Of course, this is merely an illustrative embodiment and claimed subjectmatter is not limited in scope to illustrative embodiments.

In this context, ‘IPv4’ refers to using signal packets substantiallycompatible or substantially compliant with Internet Protocol version 4,also referred to as IPv4 signal packets in this context. IPv4 isdescribed in IETF publication RFC 791 (September 1981), replacing anearlier definition (RFC 760, January 1980). IPv6 refers to using signalpackets substantially compatible or substantially compliant withInternet Protocol version 6, also referred to as IPv6 signal packets.IPv6 is described in IETF publication RFC 2460, published in December1998. Gateway device 511 in an embodiment, for example, may communicateusing IPv4 signal packets or IPv6 signal packets. It is noted, ofcourse, that claimed subject matter is not limited in scope to IPv4and/or IPv6 signal packets. Any one of a host of known or to bedeveloped signal packets, such as network communication signal packets,may be employed. Nonetheless, in this illustrative example, networkcommunications between gateway device 511 and tunnel server 560 may, forexample, comprise IPv6 signal packets. Network communications betweengateway device 511 and network device 512 may, for example, compriseIPv4 signal packets.

In an embodiment, gateway device 511, for example, may assign IPv6addresses to IPv4 network devices communicating as part of non-virtualbroadcast domain 510, without transmitting the IPv6 addresses to theIPv4 devices. In this embodiment, a device, such as a network device512, may communicate using IPv4 signal packets whereas file server 520may communicate using IPv6 signal packets. For example, network device512 may request services from file server 520. In an embodiment, gatewaydevice 511 may translate IPv4 signal packets from network device 512 toIPv6 signal packets to be forwarded via tunnel server 560 to file server520. Response signal packets transmitted to gateway device 511 may betranslated from IPv6 signal packets to IPv4 signal packets, such thatthey may be readily understood and/or processed by network device 512,communicating using IPv4 signal packets. In this context, a gatewaydevice may, for example, perform translate services so that devices of alogical broadcast domain that communicate using IPv4 signal packets maybe able to communicate with devices of a logical broadcast domain thatcommunicate using IPv6 signal packets, for example. In anotherembodiment, tunnel server 560 may provide translation between IPv4 andIPv6 signal packets, such that gateway device 511 communicates usingIPv4 signal packets without necessarily performing translation.

In one embodiment, gateway device 515, may assign IPv6 addresses toother devices communicating as part of virtual broadcast domain 514,such as, network device 516, file server 520, or virtual device 522, inaddition to already assigned IPv4 addresses. Gateway device 515 may alsoprovide updated routing tables to other devices communicating as part ofvirtual broadcast domain 514, such as, network device 516, file server520, or virtual device 522.

In another embodiment, linking with another logical broadcast domain maypotentially result in a multi-layered collection or nesting of logicalbroadcast domains. For example, in one embodiment, a virtual broadcastdomain 580 may comprise virtual broadcast domain 514 and non-virtualbroadcast domain 510, linked as previously discussed. Gateway device 515may generate and forward a broadcast domain configuration to controller506. Gateway device 515, may also forward signal packets, or derivativesthereof, from devices communicating as part of virtual broadcast domain514, to tunnel server 560.

Virtual broadcast domain 590 may comprise linking virtual broadcastdomain 580 and non-virtual broadcast domain 509. Gateway device 515,operating as a gateway device for virtual broadcast domain 580, maytransmit a broadcast domain configuration for virtual broadcast domain580 to master controller 507. Master controller 507 may request and/orreceive a broadcast domain configuration from another controller, suchas controller 506, for example. In an embodiment, therefore, gatewaydevice 515 may in effect concurrently operate as a gateway device fordifferent virtual broadcast domains. Of course, as previously described,an alternate approach may employ signal packet transmissions betweentunnel servers, such as between 560 and 561 of FIG. 3, or anotherapproach.

As discussed previously, NAT implemented by routers are by-passed forsignal packet transmissions within a private network, such as in thisexample; nonetheless, one or more NAT devices may be included forconnecting or linking a private network to the Internet, as previouslysuggested. As mentioned, a feature may include implementing a privatenetwork policy and inspection process, which may, for example, include aunified networking policy being implemented across a private network,such as, for example, implementing virus scanning, authentication,filtering, (for example, URL filtering) deep packet inspection,encryption, a firewall, any combinations thereof, etc. Likewise, aspreviously described, selected networking policies for selected portionsof a private network may be implemented as a private network policy andinspection process. Thus, for example, referring to FIG. 3, a NAT device662 coupled to tunnel server 561 is able to connect the private networkto the Internet by implementing network address translation for signalpackets outbound from TS 561 to the Internet. As shown in FIG. 3, NATdevice 563 provides a similar capability for TS 560. Likewise, the NATsmay also receive inbound signal packet transmissions which may beforwarded as appropriate. Although claimed subject matter is notnecessarily limited in scope in this respect, additional exampleembodiments of connecting to the Internet via a NAT (along with relatedtechnology) may be discussed in U.S. patent application Ser. No.13/802,529, titled “CONNECTING A CLOUD NETWORK TO THE INTERNET,” filedon Mar. 13, 2012, by Hankins et al., herein incorporated by reference inits entirety and assigned to the assignee of currently claimed subjectmatter.

For purposes of illustration, FIG. 5 is an illustration of an embodimentof a computing platform 1150 that may be employed in a client-servertype interaction, such as described infra. in connection with renderinga GUI via a device, such as a network device and/or a computing device,for example. In FIG. 5, computing platform 1130 may interface withclient 1120, which may comprise features of a conventional clientdevice, for example. Communications interface 1140, processor (e.g.,processing unit) 1160, and memory 1170, which may comprise primarymemory 1174 and secondary memory 1176, may communicate by way ofcommunication bus 1180, for example. In FIG. 5, client 1120 mayrepresent one or more or more sources of analog, uncompressed digital,lossless compressed digital, or lossy compressed digital formats forcontent of various types, such as video, imaging, text, audio, etc. inthe form physical states or signals, for example. Client 1120 maycommunicate with computing platform 1130 by way of an Internetconnection via network 1125, for example. Although the computingplatform of FIG. 5 shows the above-identified components, claimedsubject matter is not limited to computing platforms having only thesecomponents as other implementations may include alternative arrangementsthat may comprise additional components, fewer components, or componentsthat function differently while achieving similar results. Rather,examples are provided merely as illustrations. It is not intended thatclaimed subject matter to limited in scope to illustrative examples.

Processor 1160 may be representative of one or more circuits, such asdigital circuits, to perform at least a portion of a computing procedureor process. By way of example, but not limitation, processor 1160 maycomprise one or more processors, such as controllers, microprocessors,microcontrollers, application specific integrated circuits, digitalsignal processors, programmable logic devices, field programmable gatearrays, and the like, or any combination thereof. In implementations,processor 360 may perform signal processing to manipulate signals orstates and/or to construct signals or states, for example.

Memory 1170 may be representative of any storage mechanism. Memory 1170may comprise, for example, primary memory 1174 and secondary memory1176, additional memory circuits, mechanisms, or combinations thereofmay be used. Memory 370 may comprise, for example, random access memory,read only memory, or one or more data storage devices or systems, suchas, for example, a disk drive, an optical disc drive, a tape drive, asolid-state memory drive, just to name a few examples. Memory 1170 maybe utilized to store a program. Memory 1170 may also comprise a memorycontroller for accessing computer readable-medium 1175 that may carryand/or make accessible content, code, and/or instructions, for example,executable by processor 1160 or some other controller or processorcapable of executing instructions, for example.

Under the direction of processor 1160, memory, such as memory cellsstoring physical states, representing for example, a program, may beexecuted by processor 1160 and generated signals may be transmitted viathe Internet, for example. Processor 1160 may also receivedigitally-encoded signals from client 1120.

Network 1125 may comprise one or more network communication links,processes, services, applications and/or resources to support exchangingcommunication signals between a client, such as 1120 and computingplatform 1130, which may, for example, comprise one or more servers (notshown). By way of example, but not limitation, network 1125 may comprisewireless and/or wired communication links, telephone ortelecommunications systems, Wi-Fi networks, Wi-MAX networks, theInternet, a local area network (LAN), a wide area network (WAN), or anycombinations thereof.

The term “computing platform,” as used herein, refers to a system and/ora device, such as a computing device, that includes a capability toprocess (e.g., perform computations) and/or store data in the form ofsignals and/or states. Thus, a computing platform, in this context, maycomprise hardware, software, firmware, or any combination thereof (otherthan software per se). Computing platform 1130, as depicted in FIG. 5,is merely one such example, and the scope of claimed subject matter isnot limited to this particular example. For one or more embodiments, acomputing platform may comprise any of a wide range of digitalelectronic devices, including, but not limited to, personal desktop ornotebook computers, high-definition televisions, digital versatile disc(DVD) players and/or recorders, game consoles, satellite televisionreceivers, cellular telephones, personal digital assistants, mobileaudio and/or video playback and/or recording devices, or any combinationof the above. Further, unless specifically stated otherwise, a processas described herein, with reference to flow diagrams and/or otherwise,may also be executed and/or affected, in whole or in part, by acomputing platform.

Memory 1170 may store cookies relating to one or more users and may alsocomprise a computer-readable medium that may carry and/or makeaccessible content, code and/or instructions, for example, executable byprocessor 1160 or some other controller or processor capable ofexecuting instructions, for example. A user may make use of an inputdevice, such as a computer mouse, stylus, track ball, keyboard, or anyother similar device capable of receiving user actions and/or motions asinput signals. Likewise, a user may make use of an output device, suchas a display, a printer, etc., or any other device capable of providingsignals, generating visual or audio stimuli or other similar outputstimuli for a user.

Regarding aspects related to a communications or computing network, awireless network may couple client devices with a network. A wirelessnetwork may employ stand-alone ad-hoc networks, mesh networks, WirelessLAN (WLAN) networks, cellular networks, and/or the like. A wirelessnetwork may further include a system of terminals, gateways, routers, orthe like coupled by wireless radio links, and/or the like, which maymove freely, randomly or organize themselves arbitrarily, such thatnetwork topology may change, at times even rapidly. Wireless network mayfurther employ a plurality of network access technologies, includingLong Term Evolution (LTE), WLAN, Wireless Router (WR) mesh, 2nd, 3rd, or4th generation (2G, 3G, or 4G) cellular technology, other technologies,and/or the like. Network access technologies may enable wide areacoverage for devices, such as client devices with varying degrees ofmobility, for example.

A network may enable radio frequency or other wireless typecommunications via a network access technology, such as Global Systemfor Mobile communication (GSM), Universal Mobile TelecommunicationsSystem (UMTS), General Packet Radio Services (GPRS), Enhanced Data GSMEnvironment (EDGE), 3GPP Long Term Evolution (LTE), LTE Advanced,Wideband Code Division Multiple Access (WCDMA), Bluetooth, 802.11b/g/n,or other, or the like. A wireless network may include virtually any typeof now known, or to be developed, wireless communication mechanism bywhich signals may be communicated between devices, such as a clientdevice, such as a computing device and/or a network device, between orwithin a network, or the like.

Communications between a computing device and/or a network device and awireless network may be in accordance with known, or to be developedcellular telephone communication network protocols including, forexample, global system for mobile communications (GSM), enhanced datarate for GSM evolution (EDGE), and worldwide interoperability formicrowave access (WiMAX). A computing device and/or a networking devicemay also have a subscriber identity module (SIM) card, which, forexample, may comprise a detachable smart card that is able to storesubscription information of a user, and/or is also able to store acontact list of the user. A user may own the computing device and/ornetworking device or may otherwise be a user, such as a primary user,for example. A computing device may be assigned an address by a wirelessor wired telephony network operator, or an Internet Service Provider(ISP). For example, an address may comprise a domestic or internationaltelephone number, an Internet Protocol (IP) address, and/or one or moreother identifiers. In other embodiments, a communication network may beembodied as a wired network, wireless network, or any combinationsthereof.

A device, such as a computing and/or networking device, may vary interms of capabilities and/or features. Claimed subject matter isintended to cover a wide range of potential variations. For example, adevice may include a numeric keypad or other display of limitedfunctionality, such as a monochrome liquid crystal display (LCD) fordisplaying text, for example. In contrast, however, as another example,a web-enabled device may include a physical or a virtual keyboard, massstorage, one or more accelerometers, one or more gyroscopes, globalpositioning system (GPS) or other location-identifying type capability,and/or a display with a higher degree of functionality, such as atouch-sensitive color 2D or 3D display, for example.

A computing and/or network device may include or may execute a varietyof now known, or to be developed operating systems, derivatives and/orversions thereof, including personal computer operating systems, such asa Windows, iOS, Linux, a mobile operating system, such as iOS, Android,Windows Mobile, and/or the like. A computing device and/or networkdevice may include or may execute a variety of possible applications,such as a client software application enabling communication with otherdevices, such as communicating one or more messages, such as via email,short message service (SMS), and/or multimedia message service (MMS),including via a network, such as a social network including, but notlimited to, Facebook, LinkedIn, Twitter, Flickr, and/or Google+, toprovide only a few examples. A computing and/or network device may alsoinclude or execute a software application to communicate content, suchas, for example, textual content, multimedia content, and/or the like. Acomputing and/or network device may also include or execute a softwareapplication to perform a variety of possible tasks, such as browsing,searching, playing various forms of content, including locally stored orstreamed video, or games such as, but not limited to, fantasy sportsleagues. The foregoing is provided merely to illustrate that claimedsubject matter is intended to include a wide range of possible featuresor capabilities.

A logical broadcast domain may also be extended to another devicecommunicating as part of another network, such as via a virtual privatenetwork (VPN). To support a VPN, logical broadcast domain transmissionsmay be forwarded to the VPN device via another network. For example, asoftware tunnel may be created between a logical broadcast domain, and aVPN device. Tunneled traffic may, or may not be encrypted, and atunneling protocol may be substantially compliant with and/orsubstantially compatible with any past, present or future versions ofany of the following protocols: IPSec, Transport Layer Security,Datagram Transport Layer Security, Microsoft Point-to-Point Encryption,Microsoft's Secure Socket Tunneling Protocol, Multipath Virtual PrivateNetwork, Secure Shell VPN, another existing protocol, and/or anotherprotocol that may be developed.

A logical broadcast domain may communicate via signal packets, such asin a network of participating digital communications, A logicalbroadcast domain may be compatible with now known, or to be developed,past, present, or future versions of any, but not limited to thefollowing network protocol stacks: ARCNET, AppleTalk, ATM, Bluetooth,DECnet, Ethernet, FDDI, Frame Relay, HIPPI, IEEE 1394, IEEE 802.11,IEEE-488, Internet Protocol Suite, IPX, Myrinet, OSI Protocol Suite,QsNet, RS-232, SPX, System Network Architecture, Token Ring, USB, and/orX.25. A logical broadcast domain may employ, for example, TCP/IP, UDP,DECnet, NetBEUI, IPX, Appletalk, other, and/or the like. Versions of theInternet Protocol (IP) may include IPv4, IPv6, other, and/or the like.

It will, of course, be understood that, although particular embodimentswill be described, claimed subject matter is not limited in scope to aparticular embodiment or implementation. For example, one embodiment maybe in hardware, such as implemented to operate on a device orcombination of devices, for example, whereas another embodiment may bein software. Likewise, an embodiment may be implemented in firmware, oras any combination of hardware, software, and/or firmware, for example(other than software per se). Likewise, although claimed subject matteris not limited in scope in this respect, one embodiment may comprise oneor more articles, such as a storage medium or storage media. Storagemedia, such as, one or more CD-ROMs and/or disks, for example, may havestored thereon instructions, executable by a system, such as a computersystem, computing platform, and/or other system, such as a computingdevice and/or a network device, for example, that may result in anembodiment of a method in accordance with claimed subject matter beingexecuted, such as a previously described embodiment, for example;although, of course, claimed subject matter is not limited to previouslydescribed embodiments. As one potential example, a computing platformmay include one or more processing units or processors, one or moredevices capable of inputting/outputting, such as a display, a keyboardand/or a mouse, and/or one or more memories, such as static randomaccess memory, dynamic random access memory, flash memory, and/or a harddrive.

Algorithmic descriptions and/or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processingand/or related arts to convey the substance of their work to othersskilled in the art. An algorithm is here, and generally, is consideredto be a self-consistent sequence of operations and/or similar signalprocessing leading to a desired result. In this context, operationsand/or processing involves physical manipulation of physical quantities.Typically, although not necessarily, such quantities may take the formof electrical and/or magnetic signals and/or states capable of beingstored, transferred, combined, compared, processed or otherwisemanipulated as electronic signals and/or states representinginformation. It has proven convenient at times, principally for reasonsof common usage, to refer to such physical signals and/or physicalstates as bits, data, values, elements, symbols, characters, terms,numbers, numerals, information, and/or the like. It should beunderstood, however, that all of these or similar terms are to beassociated with appropriate physical quantities and are merelyconvenient labels. Unless specifically stated otherwise, as apparentfrom the preceding discussion, it is appreciated that throughout thisspecification discussions utilizing terms such as “processing,”“computing,” “calculating,” “determining”, “establishing”, “obtaining”,“identifying”, “selecting”, “generating”, and/or the like may refer toactions and/or processes of a specific apparatus, such as a specialpurpose computer and/or a similar special purpose computing and/ornetwork device. In the context of this specification, therefore, aspecial purpose computer and/or a similar special purpose computingand/or network device is capable of processing, manipulating and/ortransforming signals and/or states, typically represented as physicalelectronic and/or magnetic quantities within memories, registers, and/orother information storage devices, transmission devices, and/or displaydevices of the special purpose computer and/or similar special purposecomputing and/or network device. In the context of this particularpatent application, as mentioned, the term “specific apparatus” mayinclude a general purpose computing and/or network device, such as ageneral purpose computer, once it is programmed to perform particularfunctions pursuant to instructions from program software.

In some circumstances, operation of a memory device, such as a change instate from a binary one to a binary zero or vice-versa, for example, maycomprise a transformation, such as a physical transformation. Withparticular types of memory devices, such a physical transformation maycomprise a physical transformation of an article to a different state orthing. For example, but without limitation, for some types of memorydevices, a change in state may involve an accumulation and/or storage ofcharge or a release of stored charge. Likewise, in other memory devices,a change of state may comprise a physical change, such as atransformation in magnetic orientation and/or a physical change ortransformation in molecular structure, such as from crystalline toamorphous or vice-versa. In still other memory devices, a change inphysical state may involve quantum mechanical phenomena, such as,superposition, entanglement, and/or the like, which may involve quantumbits (qubits), for example. The foregoing is not intended to be anexhaustive list of all examples in which a change in state form a binaryone to a binary zero or vice-versa in a memory device may comprise atransformation, such as a physical transformation. Rather, the foregoingis intended as illustrative examples.

While there has been illustrated and/or described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the relevant art that various other modifications may be madeand/or equivalents may be substituted, without departing from claimedsubject matter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter.Therefore, it is intended that claimed subject matter not be limited tothe particular examples disclosed, but that such claimed subject mattermay also include all aspects falling within appended claims and/orequivalents thereof.

1.-56. (canceled)
 57. A method comprising: initiating, by a party,computer instructions for managing a first network comprising aplurality of logical broadcast domains (LBDs), wherein the managing ofthe first network includes managing the first network by use of anetworking infrastructure and/or computing infrastructure which is ownedby one or more parties other than the party initiating the computerinstructions; in response to the computer instructions, generating atleast a portion of a private address space for use within the firstnetwork, wherein the first network is for use on or above a secondnetwork having a different network address space than the privateaddress space; in response to the computer instructions, storing aconfiguration of at least one LBD of the plurality of LBDs; and inresponse to the computer instructions, provisioning a tunnel server by acontroller, wherein the tunnel server and the controller are outside theplurality of LBDs; receiving, by the tunnel server, signal packetstransmitted from a first network device and having as a destination asecond network device, wherein the signal packets are encapsulated, andwherein each of the first and second network devices are in differentLBDs of the plurality of LBDs; terminating, by the tunnel server, theencapsulation of the signal packets; re-encapsulating, by the tunnelserver, the signal packets; and forwarding, by the tunnel server, there-encapsulated signal packets to the second network device.
 58. Themethod of claim 57, wherein the first network provides outgoing networkcommunications to devices not in the first network, but inbound networkcommunications from the devices not in the first network may not bedirected to devices included in the first network.
 59. The method ofclaim 57, wherein the first network comprises at least onereconfigurable network.
 60. The method of claim 59, wherein the at leastone reconfigurable network comprises at least one real-timereconfigurable network.
 61. The method of claim 59, wherein the at leastone reconfigurable network comprises at least one geographicallyreconfigurable network.
 62. The method of claim 57, wherein the firstnetwork includes a capability to perform discovery and reflection of atleast one LBD of the plurality of LBDs.
 63. The method of claim 57,wherein the first network includes a capability to execute on demanddeployment of network services and/or network resources.
 64. The methodof claim 63, wherein the capability to execute on demand the deploymentof network services and/or network resources includes a capability formarginal network resource allocation.
 65. The method of claim 63,wherein the capability to execute on demand the deployment of networkservices and/or network resources includes a capability to changenetwork scale.
 66. The method of claim 65, wherein the change in networkscale comprises a decrease in network scale or an increase in networkscale.
 67. The method of claim 57, wherein the first network includes acapability to execute deployment of network services and/or networkresources based, at least in part, on a measured increase in networkutilization, a measured increase in network latency, a measuredreduction in network bandwidth, or any combinations thereof.
 68. Themethod of claim 57, wherein the first network includes a capability toreconfigure the first network, without human intervention, in order toimprove network performance and/or to reduce network cost.
 69. Themethod of claim 68, wherein the capability to reconfigure the firstnetwork includes a reallocation of network resources and/or geographicalreconfiguration of the first network.
 70. A system for use by a partyand for managing a first network comprising a plurality of logicalbroadcast domains (LBDs), wherein the system further is for use with afirst network device, a second network device, a second network and anetworking infrastructure and/or computing infrastructure, the systemcomprising: a tunnel server; and a controller, wherein the controller toreceive computer instructions initiated by the party for managing thefirst network, wherein the managing of the first network includesmanaging the first network by use of the networking infrastructureand/or computing infrastructure, wherein the networking infrastructureand/or computing infrastructure is owned by one or more parties otherthan the party who initiated the computer instructions, wherein, inresponse to the computer instructions, the controller to generate atleast a portion of a private address space for use within the firstnetwork, wherein the first network is for use on or above the secondnetwork, wherein the second network has a different network addressspace than the private address space, wherein, in response to thecomputer instructions, the controller to store a configuration of atleast one LBD of the plurality of LBDs, wherein, in response to thecomputer instructions, the controller to provision the tunnel server,wherein the tunnel server and the controller are outside the pluralityof LBDs, wherein the tunnel server to receive signal packets transmittedfrom the first network device and having as a destination the secondnetwork device, wherein the signal packets are encapsulated, and whereineach of the first and second network devices are in different LBDs ofthe plurality of LBDs, wherein the tunnel server to terminate theencapsulation of the signal packets, wherein the tunnel server tore-encapsulate the signal packets, wherein the tunnel server to forwardthe re-encapsulated signal packets to the second network device.
 71. Thesystem of claim 70, wherein the system further is for use with devicesin the first network and with devices not in the first network, andwherein the first network to provide outgoing network communications tothe devices not in the first network, but to prevent inbound networkcommunications from the devices not in the first network from beingdirected to the devices in the first network.
 72. The system of claim70, wherein the first network comprises at least one reconfigurablenetwork.
 73. The system of claim 72, wherein the at least onereconfigurable network comprises at least one real-time reconfigurablenetwork.
 74. The system of claim 72, wherein the at least onereconfigurable network comprises at least one geographicallyreconfigurable network.
 75. The system of claim 70, wherein the firstnetwork includes a capability to perform discovery and reflection of atleast one LBD of the plurality of LBDs.
 76. The system of claim 70,wherein the system further is for use with network services and/ornetwork resources, and wherein the first network includes a capabilityto execute on demand deployment of the network services and/or networkresources.
 77. The system of claim 76, wherein the capability to executeon demand the deployment of the network services and/or networkresources includes a capability for marginal network resourceallocation.
 78. The system of claim 76, wherein the capability toexecute on demand the deployment of the network services and/or networkresources includes a capability to change network scale.
 79. The systemof claim 78, wherein the change in network scale comprises a decrease innetwork scale or an increase in network scale.
 80. The system of claim70, wherein the system further is for use with network services and/ornetwork resources, and wherein the first network includes a capabilityto execute deployment of the network services and/or network resourcesbased, at least in part, on a measured increase in network utilization,a measured increase in network latency, a measured reduction in networkbandwidth, or any combinations thereof.
 81. The system of claim 70,wherein the first network includes a capability to reconfigure the firstnetwork, without human intervention, in order to improve networkperformance and/or to reduce network cost.
 82. The system of claim 81,wherein the capability to reconfigure the first network includes areallocation of network resources and/or geographical reconfiguration ofthe first network.
 83. An article for use by a party and for managing afirst network comprising a plurality of logical broadcast domains(LBDs), wherein the article further is for use with a tunnel server, afirst network device, a second network device, a second network and anetworking infrastructure and/or computing infrastructure, wherein thearticle comprises a non-transitory storage medium having stored thereoninstructions executable by a controller, and wherein the instructionsare executable by the controller to: receive other computer instructionsinitiated by the party for managing the first network, wherein themanaging of the first network includes managing the first network by useof the networking infrastructure and/or computing infrastructure,wherein the networking infrastructure and/or computing infrastructure isowned by one or more parties other than the party who initiated theother computer instructions; in response to the other computerinstructions, generate at least a portion of a private address space foruse within the first network, wherein the first network is for use on orabove the second network, wherein the second network has a differentnetwork address space than the private address space; in response to theother computer instructions, store a configuration of at least one LBDof the plurality of LBDs; in response to the other computerinstructions, provision the tunnel server, wherein the tunnel server andthe controller are outside the plurality of LBDs, wherein the tunnelserver to receive signal packets transmitted from the first networkdevice and having as a destination the second network device, whereinthe signal packets are encapsulated, and wherein each of the first andsecond network devices are in different LBDs of the plurality of LBDs,wherein the tunnel server to terminate the encapsulation of the signalpackets, wherein the tunnel server to re-encapsulate the signal packets,wherein the tunnel server to forward the re-encapsulated signal packetsto the second network device.
 84. The article of claim 83, wherein thearticle further is for use with devices in the first network and withdevices not in the first network, and wherein the first network toprovide outgoing network communications to the devices not in the firstnetwork, but to prevent inbound network communications from the devicesnot in the first network from being directed to the devices in the firstnetwork.
 85. The article of claim 83, wherein the first networkcomprises at least one reconfigurable network.
 86. The article of claim85, wherein the at least one reconfigurable network comprises at leastone real-time reconfigurable network.
 87. The article of claim 85,wherein the at least one reconfigurable network comprises at least onegeographically reconfigurable network.
 88. The article of claim 83,wherein the first network includes a capability to perform discovery andreflection of at least one LBD of the plurality of LBDs.
 89. The articleof claim 83, wherein the article further is for use with networkservices and/or network resources, and wherein the first networkincludes a capability to execute on demand deployment of the networkservices and/or network resources.
 90. The article of claim 89, whereinthe capability to execute on demand the deployment of the networkservices and/or network resources includes a capability for marginalnetwork resource allocation.
 91. The article of claim 89, wherein thecapability to execute on demand the deployment of the network servicesand/or network resources includes a capability to change network scale.92. The article of claim 91, wherein the change in network scalecomprises a decrease in network scale or an increase in network scale.93. The article of claim 83, wherein the article further is for use withnetwork services and/or network resources, and wherein the first networkincludes a capability to execute deployment of the network servicesand/or network resources based, at least in part, on a measured increasein network utilization, a measured increase in network latency, ameasured reduction in network bandwidth, or any combinations thereof.94. The article of claim 83, wherein the first network includes acapability to reconfigure the first network, without human intervention,in order to improve network performance and/or to reduce network cost.95. The article of claim 94, wherein the capability to reconfigure thefirst network includes a reallocation of network resources and/orgeographical reconfiguration of the first network.